Page 2 - Help on DNS issue

well unfortunately the dns server's won't let me query them, so we're going to have to test through you. When your website isn't working, I want you to do these commands for me, and tell me what you get:

Some commands to test the cache

dig @61.9.192.14 trazling.com a +norec
dig @61.9.192.14 www.trazling.com a +norec
dig @61.9.192.14 trazling.com ns +norec

Then test the resolver's recursive attempts:

dig @61.9.192.14 trazling.com a
dig @61.9.192.14 www.trazling.com a
dig @61.9.192.14 trazling.com ns

do I do this just at command prompt..because I just tried to test it and it is telling me it is not a valid command

there is a program that comes with BIND called "dig". You need to execute dig with those commandline parameters.

Alright..this is where it is getting beyond my knowledge..

I dont even know if I have bind..and if I do where is it. Is this something I have to have on my pc or do I get my host to test this. If this is the case, whenever I am down, my host can always access it.

well let's see, I don't think we discussed what operating system you have?

Microsoft Windows XP Professional - Version 5.1.2600

And does this XP computer have the DNS server on it, or is it another computer that has your domain information stored on it?

The dns is all done through my host..smartweb

well snot, I guess we're going to use nslookup then. Execute these commands instead. The first command execute nslookup. The following commands are input into the running program. I want you to copy your entire DOS output to a file and attach it for my viewing pleasure.

C:\>nslookup - 61.9.192.14

>set norec
>set type=a
>trazling.com
>www.trazling.com
>set type=ns
>trazling.com

>set rec
>set type=a
>trazling.com
>www.trazling.com
>set type=ns
>trazling.com

And I do this next time it goes down yes..not a problem, and thank you again.

Update..I have not this issue happen to me since the last time, hence no response. Have had a couple of people who did have the issue, but it seems to resolve itself much quicker now. But no where near the amount of problems I was having..so those setting changes have had some effect. Will update again only when the problem occurs for me again.

Thanks

I spoke too soon..having the problem right now, so did the above testing. I have attached the results for you. The first section was a test I did while it was working..the second section is the test while it was not working.

appreciate your help!

Excellent, very educating. Well done with the testing. You followed instructions PERFECTLY. I'm shocked, my name could be LoudlyEcstatic at this moment.

So what did all that spew tell me? It told me that everything appears to be working fine except your caching server is returning server failures. It is NOT cause of badly cached information cause the test showed that there was nothing in the cache before you finally made a recursive query and got the server failures.

Now the server failure message could mean one of two things. Either the server itself had an internal problem (low memory, that sort of thing) or the authoritative servers (ns3.aaawebonline.net, ns4.aaawebonline.net) could also be returning server failures due to some internal problem or misconfiguration.

So let's see which one it is. Our testing did an admiral job of fully investigating the caching server, however, we failed to test the authoritative servers. I wish I thought of doing this at the time.

The next time your domain becomes unavailable I want you to click on these links and tell me what you get:

http://www.dollardns.net/cgi-bin/dn...ype=A&submit=DS
http://www.dollardns.net/cgi-bin/dn...e=ANY&submit=DS

http://www.dollardns.net/cgi-bin/dn...ype=A&submit=DS
http://www.dollardns.net/cgi-bin/dn...e=ANY&submit=DS

Now if I were to make a prediction, I bet that one or both of those servers go temporarily wacky and will return "Server Failure". If this is the case, then we can discuss what to do about it.

Well I am still down so I clicked those links and no server failures came up..it all appeared to be fine..(have copied results into attached text file for you)

I can still get to my site via ip address, just not domain name, so server is up..got into my control panel (which is by ip address) and this is server status...

Server Status

apache (1.3.29 (Unix)) up
bind (9.2.1) up
cpanel up
cppop up
exim (exim-4.24-30_cpanel_stmpcontrol_antivirus_rewrite_mailman2) up
eximstats up
ftpd up
imap up
mysql (4.0.18-standard) up
syslogd up
webmail up
whostmgr up
cpsrvd up
Server Load 0.55 (4 cpus)
Memory Used 20.5 %
Swap 0.948 %
Disk sda2 (/) 13 %
Disk hda1 (/backup) 14 %
Disk sda1 (/boot) 22 %
Disk sda7 (/home) 31 %
Disk sda5 (/usr) 28 %
Disk sda6 (/var) 15 %

Yet my mail is not working either..

Well all I have to say is complain to your ISP. We get server failures on them, but not on your host servers. Your DNS configuration is perfect. I say it's your ISP's fault. See what they have to say.