I've got a strange problem with all my domains on my server.

Sometimes, well it happens quite often, I get a DNS Lookup Error for all my domains on the server, and a few hours later it is back to normal without me doing anything..
Strangely enough, my nameservers are always available
The nameservers and the A record for each domain seem ok though..

Two domains that have the problem:
http://www.dromedaris.be
http://www.volcano.be

Anyone knows what the problem could be and what I can do to solve it?

It was okay for a few hours, but now the same problem again :(

I think you need to register ns1/2 fqrgohosting.com with internic

Also make sure you have A records in the zone records of fargohosting.com for n1 & ns2

I already have A records for my nameservers...
And I have registered my nameservers more than a week ago.

but why is a dns query of your domains returns lameservers? please check if both ips in the A records and root are same..

i wont be online tomorrow but i will try to look at why on Wednesday

send me a mail if you havent solved it by then :)

The name servers are registered because the 'glue' records (IP's)for them are returned when you query the GTLD servers...

sh-2.05$ dig +norec fargohosting.com @E.GTLD-SERVERS.NET

; <<>> DiG 9.2.1 <<>> +norec fargohosting.com @E.GTLD-SERVERS.NET
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44961
;; flags: qr; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 2

;; QUESTION SECTION:
;fargohosting.com. IN A

;; AUTHORITY SECTION:
fargohosting.com. 172800 IN NS NS1.fargohosting.com.
fargohosting.com. 172800 IN NS NS2.fargohosting.com.

;; ADDITIONAL SECTION:
NS1.fargohosting.com. 172800 IN A 205.214.72.97
NS2.fargohosting.com. 172800 IN A 205.214.72.98


Its the fact that your name servers are not giving out the A record.......

sh-2.05$ dig +norec fargohosting.com @NS1.fargohosting.com

; <<>> DiG 9.2.1 <<>> +norec fargohosting.com @NS1.fargohosting.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61237
;; flags: qr ra; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 0

;; QUESTION SECTION:
;fargohosting.com. IN A

;; AUTHORITY SECTION:
fargohosting.com. 98262 IN NS NS1.fargohosting.com.
fargohosting.com. 98262 IN NS NS2.fargohosting.com.

;; Query time: 1 msec
;; SERVER: 205.214.72.97#53(NS1.fargohosting.com)
;; WHEN: Mon Sep 16 12:26:54 2002
;; MSG SIZE rcvd: 70


yellow_belly

Could it have something to do with the fact that I'm runnnig BIND 9?

I submitted a support ticket with my dedicated provider about 6 hours ago, no solution yet.

When I do "dig @ns2.fargohosting.com fargohosting.com" locally I don't get errors, but when I do it somewhere else I get SERVFAIL.

Dnsreport.com still gives errors.

VO Support told me to reinstall BIND (is that all they can say??), that didn't solve the problem.

can you post the zone file.....

yellow_belly

Here is your problem (hopefully)...... the dns system is giving this out for your registered name servers....


;; ADDITIONAL SECTION:
NS1.fargohosting.com. 172800 IN A 205.214.72.97
NS2.fargohosting.com. 172800 IN A 205.214.72.98

but those 2 IP addresses do not root to VO - so either you need to change the IP addresses that are registered for your name servers to the proper ones, or if these are the proper IP addresses then get VO to route them to your server.

As VO changed all their IP addresses a while ago when they moved NOC I would hazard a guess the IP addresses above are wrong (but I have been known to be wrong :D )

yellow_belly

yellow_belly, it doesn't seem to be that problem.. Answer from the VO support tech...

I wish that were the problem :) Those IP's are in fact VO's and they are bound to the ethernet interface of your server.

Do me a favor and when you see the issue pop up again, open a DOS window and telnet to the DNS port like so:

telnet 205.214.72.97 53

If you get "connection refused" then we'll know for sure that the DNS server is shutting down for some reason. I'll keep the ticket open and await your response. Thanks!

So I did the telnet, no "connection refused" however.

dont know what I did wrong with the traceroute then ???? must have had a brain fa*t ????

Can you post fargohosting.com 's zone file - running out of ideas here fast - but not giving in :D

yellow_belly

; Zone File for fargohosting.com
@ 14400 IN SOA ns1.fargohosting.com. root.ns1.fargohosting.com. (
1031402856
28800
7200
3600000
86400
)

fargohosting.com. 14400 IN NS ns1.fargohosting.com.
fargohosting.com. 14400 IN NS ns2.fargohosting.com.
fargohosting.com. 14400 IN A 205.214.72.96

localhost.fargohosting.com. 14400 IN A 127.0.0.1

fargohosting.com. 14400 IN MX 0 fargohosting.com.

mail 14400 IN CNAME fargohosting.com.
www 14400 IN CNAME fargohosting.com.
ftp 14400 IN CNAME fargohosting.com.
ns1 14400 IN A 205.214.72.97
ns2 14400 IN A 205.214.72.98
anubis 14400 IN A 205.214.72.96


The only thing VO support did in the last 36 hours was asking me if I could telnet to the nameservers.... Great support, right?

Zone file looks o.k. - just thinking out aloud now and re-reading all the posts a good recap of the problem is this.......

1. your name servers 'sometimes' work'

2. your name severs 'sometimes' do not work

3. the name servers IP addresses are correct and route to your server

4. your name servers are correctly registered (glue records are returned)

5. when the problem occurs your name servers are still working and available (you proved this with telnet)

6. the zone file for fargohosting.com looks o.k.

7. querying your name servers by IP address (as opposed to ns1.fargohosting.com) returns the same results

All the easy solutions have been tried so groping in the dark now, just so we know all the facts....

how long have you had the server ?

you registered your name servers recently so have you had name servers working correctly on this server before ?

if so have you done anything recently to the server at all e.g. you say you are running bind 9 - has this recently been upgraded. ?

how do you add domains, cpanel, webmin etc.

anything else you think may be useful to know ???

desperate yellow_belly

yellow_belly, thanks for your help here, but I forgot to mention that the problem is solved..

There were double bound IP's out on the VO network. Another server is trying to use the same IP's that I use for my NS. An issue completely on their side, we could do nothing about it.

It took VO-support about 2 days to find the problem, and another 4 days to solve it... Not very fast IMO.

Anyway, thx again yellow_belly and motley fool for your input :)

Bram...

Funny I found you here...I was the guy that had the IP's and was having a similar problem. I worked with VO to solve it. Seems that you and I purchased IP blocks at the same time, and ended up with the same ones...I had a user that would occasionally get that generic apache page ('Hey, it worked.....')

It was an occasional thing and hard to trace. Once I caught it happening, I returned an error with fargohosting in it. I then ran DNS check on your domain name and saw your second nameserver was using the same IP as our user...I sent this to VO and they resolved it ;)

Interesting :eek: that was certainly the strangest DNS problem that I have come across :D

yellow_belly

LOL...Tell me about it. VO told me they would look into how the mix-up occured. All I know is that Bram and I picked up our IP's at about the same time....I had just set the server up and was putting new accounts on there...then the one client had the problem and thats how we discovered it. That entire IP block was removed from our server and Bram is now safe to use them...it was rather strange, though...drove me nuts trying to figure out what was going on, and I'm sure it was much worse for Bram...

Rather late reply, but here goes..

It drove me nuts, seriously, sometimes it worked, and sometimes it didn't

Really funny that the person who was using the IP is also on WHT, it's a small world ;)

Well Tom, thanks for sending the solution to VO support!

LOL...I was wondering whatever happened to you. Yeah...that was the thing here...sometimes it worked sometimes it didn't. It wasn't untill I ran a DNS check on the IP and found your nameservers bound to it :)