<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Hi,</p>
    <p>I would try tomorrow, but my rpi machines received hostname set
      from dnsmasq. I used static allocations only for my testing. Can
      you share at least relevant part of dnsmasq configuration?</p>
    <p>Does it have dhcp-host record for that machine?<br>
    </p>
    <div class="moz-cite-prefix">On 10/25/21 16:00, Shrenik Bhura wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CANKp9xfVfk0mNTvaXrzAVxM1zfBOQGqvUNuwfvqf1mxS_nc1nA@mail.gmail.com">
      <div dir="auto">
        <div dir="auto"><br>
        </div>
        <div dir="auto">
          <div class="gmail_quote" dir="auto">
            <div dir="ltr" class="gmail_attr">On Mon, 25 Oct, 2021,
              01:24 Matthias May via Dnsmasq-discuss, <<a
                href="mailto:dnsmasq-discuss@lists.thekelleys.org.uk"
                rel="noreferrer noreferrer noreferrer" target="_blank"
                moz-do-not-send="true" class="moz-txt-link-freetext">dnsmasq-discuss@lists.thekelleys.org.uk</a>>
              wrote:<br>
            </div>
            <blockquote class="gmail_quote">On 21/10/2021 13:05, Shrenik
              Bhura wrote:<br>
              > May be the code that logs this line needs to be
              checked if it is just printing part of the complete
              hostname i.e. IP<br>
              > address.<br>
              > <br>
              <br>
              Hi Shrenik<br>
              <br>
              The code is doing what it is supposed to do.<br>
              <br>
              Please take a look at the definition of a hostname and
              what makes up an FQDN.<br>
              * <a href="https://en.wikipedia.org/wiki/Hostname"
                rel="noreferrer noreferrer noreferrer noreferrer
                noreferrer" target="_blank" moz-do-not-send="true"
                class="moz-txt-link-freetext">https://en.wikipedia.org/wiki/Hostname</a><br>
              * <a
                href="https://en.wikipedia.org/wiki/Fully_qualified_domain_name"
                rel="noreferrer noreferrer noreferrer noreferrer
                noreferrer" target="_blank" moz-do-not-send="true"
                class="moz-txt-link-freetext">https://en.wikipedia.org/wiki/Fully_qualified_domain_name</a><br>
              <br>
              Valid characters for hostnames are:<br>
              * ASCII(7) letters from a to z<br>
              * The digits from 0 to 9<br>
              * The hyphen (-)<br>
              * A hostname may not start with a hyphen<br>
              * When following the old RFC 952, a hostname may not start
              with a digit.<br>
              <br>
              The dot '.' is used to concatenate the different domain
              labels.<br>
              <br>
              In your case you are using an IP address as hostname which
              is not a valid hostname.<br>
              The first dot in the name you provide is interpreted as
              domain label separator, thus the hostname is 192.</blockquote>
          </div>
        </div>
        <div dir="auto">
          <div class="gmail_quote" dir="auto">
            <blockquote class="gmail_quote">
              <br>
              BR<br>
              Matthias</blockquote>
          </div>
        </div>
        <div data-smartmail="gmail_signature" dir="auto">
          <blockquote><br>
          </blockquote>
        </div>
        <div data-smartmail="gmail_signature" dir="auto">
          <div data-smartmail="gmail_signature" dir="auto"><br>
          </div>
          <div data-smartmail="gmail_signature" dir="auto">Hi All,</div>
          <div data-smartmail="gmail_signature" dir="auto"><br>
          </div>
          <div data-smartmail="gmail_signature" dir="auto">Clarifying on
            the last two posts -</div>
          <div data-smartmail="gmail_signature" dir="auto"><br>
          </div>
          <div data-smartmail="gmail_signature" dir="auto">> In your
            case you are using an IP address as hostname which is not a
            valid hostname.</div>
          <div data-smartmail="gmail_signature" dir="auto"><br>
          </div>
          <div data-smartmail="gmail_signature" dir="auto">> the
            problem here is the client looks to be misconfigured if it
            is telling the</div>
          <div data-smartmail="gmail_signature" dir="auto">server its
            name is an IP address... they are very different...</div>
          <div data-smartmail="gmail_signature" dir="auto"><br>
          </div>
          <div data-smartmail="gmail_signature" dir="auto">No, I am not
            using such an IP address anywhere as a hostname. </div>
          <div data-smartmail="gmail_signature" dir="auto">Nothing on
            the server is configured to set the same. </div>
          <div data-smartmail="gmail_signature" dir="auto">The Raspberry
            Pi client is netbooting, so nothing on the client side could
            be setting it. </div>
          <div data-smartmail="gmail_signature" dir="auto">Or may be it
            is something in the Raspberry Pi 4B and 400 netbooting
            firmware which could be responsible for this, if it is not
            something wrong with dnsmasq? </div>
          <div data-smartmail="gmail_signature" dir="auto"><br>
          </div>
          <div data-smartmail="gmail_signature" dir="auto">See - <a
href="https://drive.google.com/file/d/1WmbdcjFf6OYU-lcwwHw2LM40eSEIvllL/view?usp=drivesdk"
              moz-do-not-send="true" class="moz-txt-link-freetext">https://drive.google.com/file/d/1WmbdcjFf6OYU-lcwwHw2LM40eSEIvllL/view?usp=drivesdk</a></div>
          <div data-smartmail="gmail_signature" dir="auto"><br>
          </div>
          <div data-smartmail="gmail_signature" dir="auto">May be
            something in the dns handling implementation within dnsmasq
            which doesn't differentiate the absence of a hostname uses
            the same IP address that has been served to the client to
            play along, eventually truncating what it calculates as the
            domain part (168.67.53) from the fqdn (i.e. after the first
            . "dot"), and serving just the hostname (192). This sequence
            is visible in the snap above.</div>
          <div data-smartmail="gmail_signature" dir="auto"><br>
          </div>
          <div data-smartmail="gmail_signature" dir="auto">If this is
            still not clear then I suggest that the only way to
            understand this situation best is by netbooting a RPi 4B
            yourself from a dnsmasq powered authoritative dhcp server.</div>
          <div data-smartmail="gmail_signature" dir="auto"><br>
          </div>
          <div data-smartmail="gmail_signature" dir="auto">Do note that
            this is not reproducible with a x86 client.</div>
          <div data-smartmail="gmail_signature" dir="auto"><br>
          </div>
          <div data-smartmail="gmail_signature" dir="auto"><span
              class="gmail_chip gmail_plusreply" dir="auto"><a
                href="mailto:pemensik@redhat.com" moz-do-not-send="true">@Petr
                Menšík</a></span><span> </span> may be you will be able
            to replicate this easily as you have gone through this
            sequence while nailing the UEFI+non-proxy bug.</div>
          <div data-smartmail="gmail_signature" dir="auto"><br>
          </div>
          <div data-smartmail="gmail_signature" dir="auto">Regards,</div>
          <div data-smartmail="gmail_signature" dir="auto">Shrenik</div>
        </div>
        <div data-smartmail="gmail_signature" dir="auto"><br>
        </div>
        <div data-smartmail="gmail_signature">Regards,<br>
          Shrenik</div>
      </div>
    </blockquote>
    <pre class="moz-signature" cols="72">-- 
Petr Menšík
Software Engineer
Red Hat, <a class="moz-txt-link-freetext" href="http://www.redhat.com/">http://www.redhat.com/</a>
email: <a class="moz-txt-link-abbreviated" href="mailto:pemensik@redhat.com">pemensik@redhat.com</a>
PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB</pre>
  </body>
</html>