I've done something horrible to my DNS. :(

[karak2]

Well here it is - was a perfectly working debian install, but somehow I killed name resolution...

I think it had something to do with uninstalling avahi-daemon before I knew what it did, but after that and a reboot, it won't even resolve DNS, or for that matter bring up the eth1 interface at boot time, I have to connect a keyboard and monitor and bring up eth1 with ifconfig, but even that doesn't let it resolve dns, the only way it seems to work is if I run dhclient, but that pulls a private IP from my wireless router instead of using the static public IP that I've got...

Anyone have any ideas? I can post logs and such if necessary but I really could use some direction here...

[jaijai]

Hello,

You can use yum to install DNS avahi-daemon. "yum install named". Yes, do let me know, if this works?

[kavalakala]

What does your /etc/resolv.conf contain?
Does any hostname resolve when using for example dig (package dnsutils) like

dig @<yournameserver_ip_address> google.com

It should give you something like

;; ANSWER SECTION:
google.com.             45      IN      A       74.125.45.100
google.com.             45      IN      A       209.85.171.100
google.com.             45      IN      A       72.14.205.100

Does the connection really become active, in other words, can you ping or otherwise transfer data to ip addresses after bringing the if active manually?