Bind will not answer DNS requests
I am hoping that someone can help me on this. I have been beating away at this for many hours.
I had my primary dns server stop answering dns requests yesterday after a power outage at it's data center. I have it co-located in Michigan and I am in Oklahoma. All the dns requests fell back onto my windows server 03 box here in OK. I decided to take one of my other co-located servers that was not doing anything anymore (also in Oklahoma) and make it the new primary dns (ns1). Long story short, I replaced the stock bind with "bind9-base-18.104.22.168" and managed to get everything functioning including rndc but it will not answer a normal dns request. I can dig it locally and from one of my other bsd boxes and it responds with the correct record. I can go to "dns stuff" site and it will respond...but if I try pinging, I can't get any domains to resolve. I try to browse to a page that it is hosting dns for and I get nowhere. I have not deeply researched dig but I am guessing that dig and the "dns stuff" site may be sending requests through tcp when the real world is sending through udp. Anyone with any ideas?
BTW. This name server is not used except as a master authorative dns server for a hand full of domains.