Topic: Broken DNS? (Page 1 of 1)

Ok all you linux gurus... I'm stumped again.

I think I made it through the yum 404 issues I was having, but now it's broke in a new way.

I'm trying to build a package from source so I can get a static version of it, so I download the source, extract it, and ./configure isn't happy. "checking whether build environment is sane... error: newly created file is older than distributed files'
I check the system time and get: Monday, Jan 1 20:30:37 2007

... Not a problem, I've had to use rdate before to sync the system time.
'rdate -s time-b.nist.gov' fails: "Assertion 'hent->h_addrType == 2' failed"

I did some checking and found source to rdate, found the offending assertion...
assert(hent->h_addrType == AF_INET);

(hent is the host entry of the NTP server that is passed to rdate)

So apparently it thinks the NTP server isn't IPv4... ?

I try to ping the server out of curiosity and lack of other ideas. Ping returns good, but something's funny with it:
PING time-b.nist.gov (127.0.0.1) 56(84) bytes of data.

... It resolved the host time-b.nist.gov to be 127.0.0.1
I try to ping it by it's real IP and get nothing back.

Anyone have any thoughts on why everything resolves to the loopback address? I checked the DNS servers and they're the same for another machine that's working fine.

LF

--

Any sufficiently advanced bug is indistinguishable from a feature.

sounds like something went wacky with you hent stuff you did up there. Not sure what that was all about though. You said

quote:

---

Lord_Fukutoku said:

So apparently it thinks the NTP server isn't IPv4... ?

---

not following you there.

However, when I ping that from any box it times out. No big deal since you can block ping requests to any computer with some configuration.
What do you mean that it doesn't think that NTP server isn't IPv4?

Later,

C:\

Lord_Fukutoku,
I'm a little confused. The symptoms you're getting sound as if you haven't set up the NIC to aquire an IP from your DHCP server. Are you using DHCP or atatic IPs on your LAN? Do I understand that you've already downloaded some source files from the InterNET using that machine? If so, it's odd that you are having difficulty reaching other computers on your network with ping.

The only suggestion I have, without more information, is to look in /etc/hosts and see if there are extra entries using 127.0.0.1.

.



-- not necessarily stoned... just beautiful.

quote:

---

CPrompt said:

What do you mean that it doesn't think that NTP server isn't IPv4?

---

The assertion was failing in rdate (assert(hent->h_addrType == AF_INET), so it would appear that my machine didn't think the machine it was connecting to (supposedly) was using standard IP (vs IPv6 for instance). The ping issues afterwards though, seem to make this part somewhat moot I suppose.

Found this:

quote:

---

/usr/include/linux/socket.h:#define AF_INET 2 /* Internet IP Protocol */
/usr/include/linux/socket.h:#define AF_INET6 10 /* IP version 6 */
/usr/include/linux/socket.h:#define PF_INET AF_INET
/usr/include/linux/socket.h:#define PF_INET6 AF_INET6
/usr/include/bits/socket.h:#define AF_INET PF_INET
/usr/include/bits/socket.h:#define AF_INET6 PF_INET6

---

here: http://www.unidata.ucar.edu/support/help/MailArchives/ldm/msg01456.html



hyperbole: No, it isn't using DHCP. Everything on these boxes is static. I double-checked the configs for all three NICs, and all seems well.
These boxes don't have direct internet access right now (although normally they do). I'm downloading packages to another machine and using SSH to copy/build/run everything on these until they're ready. I can SSH into both boxes using their IP, but 'ping -a' is returning some other host on the network for that address, so I think someone might've taken my addresses. I'm working on getting that sorted now. Hopefully that'll fix it, but I still don't quite understand why another box with my IP would cause mine to think everything resolved to 127.0.0.1 ...

[edit: fixing the IP conflicts didn't help...


--

Any sufficiently advanced bug is indistinguishable from a feature.

(Edited by Lord_Fukutoku on 03-18-2009 17:27)

(Edited by Lord_Fukutoku on 03-18-2009 17:37)

i just need to ask a question here. It sounds like you are going through a lot of trouble to do something very simple. Why give them static IP's "until they are ready" and such?

Later,

C:\

They'll always have static IPs, they're just cutoff from the outside world right now until we get everything we need installed and configured. They don't have any video out, so we only have shell access, so ssh seemed the way to go to copy packages across and build what we need.

--

Any sufficiently advanced bug is indistinguishable from a feature.