0

Sorry for bad english. I have a DHCP server router with IP 192.168.0.254 Everything goes well, but my phone and my tablet gets a very strange DNS 1 server: 80980492081

Here is a screenshot:

enter image description here

This is very strange and is getting me mad. I don't know where that strange DNS 1 server comes from. My DHCP server settings are right.

My phone is a Samsung Galaxy S5

Does anybody know what is happening?

Thank you.

9
  • 1
    DHCP? Aren't you showing the manual settings screen?
    – user1686
    Nov 21, 2019 at 10:51
  • Yes. That's because to show what dhcp parameters got the phone. 1st I set as dhcp. 2nd connect, 3rd, set as static to view what parameters got.
    – peperfus
    Nov 21, 2019 at 12:15
  • But this window doesn't show DHCP received parameters. Even if you do what you described, it only shows previously entered manual parameters.
    – user1686
    Nov 21, 2019 at 12:25
  • I do this because IP tools doesn't show this DNS 1 server. It shows the supposed right settings. Nonetheless when I try to ping a host defined in my DNS server I get error, because my phone isn't using my DNS server :(
    – peperfus
    Nov 21, 2019 at 12:27
  • 1
    From GUI set to DHCP. Switch WiFi OFF and ON. Execute this command in adb shell: dumpsys connectivity | grep CONNECTED | grep -o 'Routes: .* DnsAddresses: [^ ]*'. This shows you the DNS and default gateway addresses received from DHCP server. Nov 21, 2019 at 13:12

1 Answer 1

0

An IPv4 address is a 32bit number. The common way to print an IPv4 address is to split it into 4 8bit blocks and separate them with a dot.

However an IPv4 address is also valid in it's decimal/integer representation. This decimal representation is used for your DNS IP address: 80980492081.

Converting the number in the common IPv4 address format ends up with the IP address: 218.208.63.49.

https://www.vultr.com/resources/ipv4-converter/?ip_address=80980492081

3
  • 3
    Only if you use converters which do not check the input at all. 80980492081 or hex 0x12DAD03F31 is at least a 37-bit number and does not make sense as an IP address – Vultr's converter quietly ignores the extra parts. (Besides, why would the software arbitrarily show an IP address in full-decimal format?)
    – user1686
    Nov 21, 2019 at 13:13
  • @grawity Good catch. Would be interesting what Linux/Android does in such a case. If it just ignores the bits higher than 32 (uses the number modulo 2^32)?
    – Robert
    Nov 21, 2019 at 13:16
  • Maybe, but in that case the number cannot possibly be coming from DHCP (as the packet format only has a 32-bit field) – it can only come from manual input or from some unusual software bug.
    – user1686
    Nov 21, 2019 at 13:20

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .