Mijn SOA staat niet helemaal goed in DNS??

[Verwijderd]

Beste Tweakers,

Zit met een probleempje op mijn windows 2003 server, ik draai een active directory integrated DNS server en alles schijnt echt goed te werken hoor, alle clients kunnen surfen, netwerkshares werken perfect, geen timeouts, inloggen op domain gaat met lightningspeed, intern netwerk gaat tegen een gemiddelde snelheid van 40Mb/s, dus ben al blij zat eigenlijk maar is 1 ding dat me gister in mijn routerlogs opviel en hier zou ik toch wel graag een verklaring willen zien.

ik heb voor dit probleem van mij al een post aangemaakt en zou dus die vraag hier gewoon willen plakken, tis int engels maar denk dat meeste van jullie dit wel zullen begrijpen, dus hier gaat ie dan mijn big question,

I just found out that I have a problem with my SOA cuz sometimes I got this strange IP adress my DNS SERVER was trying to go to, so I googled a bit and came across this awesome page. So I did what was described below between quotes,

To get your SOA data, you can use NSLOOKUP or DIG (or any other program, or a web site, that can query DNS records from a nameserver you choose). You need to use your domain as the domain name to query, query for the SOA record, once for each nameserver on the list you wrote down.
Using NSLOOKUP, enter "server nameserver.example.com" (do this once for each nameserver on your list, replacing "nameserver.example.com" with one nameserver at a time). Then, type "set type=SOA". Finally, type your domain name ("example.com"). You will see the SOA record for your domain.
Using DIG, enter your domain name as the domain name to query, and enter each server from the list you wrote down (one at a time), and look at the SOA or "Zone of Authority" section.
Problem? Make sure that the SOA record returned by each name server is identical. If the serial numbers are different, you will have to wait up to the number of seconds listed in the "refresh" section of the nameserver with the lower serial number for it to get updated (or more time if the secondary nameserver can't reach the primary). If the primary nameserver has a lower serial number than a secondary, you have a serious problem that you will need to fix. If the serial numbers are the same, but other data is different, you have a serious problem -- your primary was updated without updating the serial number (update the serial number and the problem will get fixed).
Problem? The SOA record MUST be the FIRST record in your zone file, and MUST also be the LAST record in your zone file. It must appear only those two times, and both of the entries must be identical. This can be verified correctly only on the nameserver itself; the procedure varies depending on the software you use.

So I typed in following order,

Nslookup

That returned following lines of text(which is the correct IP and FQDN for my windows 2003 server running DNS cuz when I ping Filehosting it comes back with a reply on correct IP and it also says "pinging Filehosting.rambo.local.com"),

Default Server: Filehosting.rambo.local.com
Address: 192.168.1.82

Then I continued what was described in that article, so next up I typed this,

server Filehosting.rambo.local.com

and when I entered it said the following,

Default Server: Filehosting.rambo.local.com.local.com
Address: 63.251.207.31
And this IP adress and FQDN is all wrong, that IP is an external IP and it has all of a sudden added another local.com behind my primary DNS FQDN

So I continued and typed the last piece of text, so I entered the following,
set type=SOA
rambo.local.com
It then came back with this same fucked up shit,
Filehosting.rambo.local.com.local.com
Address: 63.251.207.31
DNS request timed out.
Timeout was 2 seconds.
DNS request timed out.
Timeout was 2 seconds.
*** Request to Filehosting.rambo.local.com.local.com timed-out

And ofcourse its blocked cuz I do not allow outbound weirdness to unknown crappy servers in my router(thank God).

So the big question now is, how do I fix my DNS settings so that my server comes back with my correct information, so,

Filehosting.rambo.local.com

instead of this,

Filehosting.rambo.local.com.local.com

Thnx to any and all who can shed some light on the matter, just ask me for any other info you need to troubleshoot and I will provide.

PS : Need to add one more thing to this, I just checked my routerlogs, and I also see 4 different root server IP's listed there as being TRAFFIC DENIED. I have set up two of my ISP's DNS servers as forwarders in my DNS server, so how in flipping hell is my server also trying to go to these root servers(and all root servers are blocked in my router, only my ISP's DNS servers are allowed outbound in my router). So my clients can indeed surf the internet.

Also, that 63.251.207.31 is not a root server, its trying to go to this Filehosting.rambo.local.com.local.com domain on the internet instead of sending the request to Filehosting.rambo.local.com(which is the FQDN of my windows 2003 server).

Hoop dat een of andere guru hier het licht ziet

[elevator]

Sorry, maar je vraag naar het Nederlands vertalen is toch echt wel het minste wat je kan doen