main domain and ns problems

A

alloin

Verified User
Joined
Feb 19, 2006
Messages
14
Hi there,

I have my own dedi server with debian running with DA.

I am trying for more then a week to set up my main domainname and nameservers.

My domain is antwanserver.be, i have 2 ip's 85.92.130.132 and 85.92.130.132.

I've tried everything but it seems it doesn' t work.

I've added the 2 ip's in DA admin level, I added nameserver to the ip's in reseller lvl and created the domain in user lvl.

As i check on http://www.dnsreport.com/tools/dnsreport.ch?domain=antwanserver.be
it shows following 3 fails and 2 warns...

Can someone help me plz, cuz i need to get my sites online quickly...

Thnx in advance
 
Jon, BIND nameservers have no problem with hosting any top-level domain, so I'm not sure what you mean.

Many top-level domains require that nameservers be on separate IPs or even on separate networks, but that's got nothing to do with nameservers not working.

alloin, did you read those errors and attempt to understand them?

1st WARN: You don't have NS records in your DNS at the nameserver at 85.92.130.133.

1st FAIL: Your nameserver at 85.92.130.133 didn't respond with any records at all.

2nd FAIL: Lame Nameservers ... this means that your servers don't have records for the domain. They're not authoritative.

3rd FAIL: Missing nameservers 2 ... You don't have NS records for your nameservers.

2nd WARN: Nameservers on separate class Cs ... I mentioned this above in my note to Jon.

4th FAIL: There's no valid SOA records.

Looking at all the missing records and the fact that your nameservers are not returning authoritative responses (Lame Nameservers), it appears that your nameserver cannot find it's zone files.

Have you looked at the DNS records from the DA admin logon screen? Do they contain the A records, SOA record, and NS records (at a minimum)?

If everything appears right you'll have to have someone who understands DNS and linux systems administration log into your system to figure out what's wrong, as you do have proper DNS delegation from the .be root servers.

Jeff
 
this is filled in at the dns administration:

antwanserver.be. A 85.92.130.132
ftp A 85.92.130.132
localhost A 127.0.0.1
mail A 85.92.130.132
ns1.antwanserver.be. A 85.92.130.132
ns2.antwanserver.be. A 85.92.130.133
pop A 85.92.130.132
www A 85.92.130.132
antwanserver.be. NS ns1.antwanserver.be.
antwanserver.be. NS ns2.antwanserver.be.
mail MX 10
antwanserver.be. TXT "v=spf1 a mx ip4:85.92.130.132 ?all"
 
Jon, BIND nameservers have no problem with hosting any top-level domain, so I'm not sure what you mean.
Click to expand...

I'm not sure where I picked that up. It might have been with the domain registrar or dns management service in my "the early years".
 
Last edited:
i've tried it with zoneedit nameservers and then it works perfect...

Any idea what to do ?

thnx
 
First make sure your nameserver works; try using it to look up any domain (I've done this; it works for me).

Set up exactly the same records on your server as work on the zoneedit serers, paying special attention to the "." character at the end of all full domain names. Also set up A records and NS records for your nameservers in their zonefile.

Add the two nameservers at your registrar (I can't tell you how to do it; all registrars do it differentlly).

Change the settings so the domain will use it's own nameservers.

Wait until the changes propagate (anywhere from almost instantly to 72 hours or so).

Then try them.

Jeff
 
Hi,

thank you all for the information but i found the problem.

I opened putty, logged in and typed ndc restart (restart named) and bam !!!

It works now !!! :rolleyes:
 
It seems that named (the BIND daemon) didn't restart when you made changes to the zone files.

Did you make your changes from the shell, or from the web-based DA interface? If from the shell you always have to restart BIND. If from the web-based DA interface, the interface should have restarted it for you.

Jeff
 
I've made the changes from DA, so there must have been a problem with restarting...

*edit* anyone know how to fix this, everytime i make changes or add a new domain, i must restart named manually
 
Last edited:
Check your /var/log/messages file to see if BIND is attempting to restart, and if so, if it gives out any error message(s).

Jeff
 
getting this in system messages:

Mar 2 00:50:07 darkdemonserver -- MARK --
Mar 2 01:10:07 darkdemonserver -- MARK --
Mar 2 01:30:07 darkdemonserver -- MARK --
Mar 2 01:50:07 darkdemonserver -- MARK --
Mar 2 02:10:08 darkdemonserver -- MARK --
Mar 2 02:30:08 darkdemonserver -- MARK --
Mar 2 02:50:08 darkdemonserver -- MARK --
Mar 2 03:10:08 darkdemonserver -- MARK --
Mar 2 03:30:08 darkdemonserver -- MARK --
Mar 2 03:50:08 darkdemonserver -- MARK --
Mar 2 04:10:08 darkdemonserver -- MARK --
Mar 2 04:30:08 darkdemonserver -- MARK --
Mar 2 04:50:08 darkdemonserver -- MARK --
Mar 2 05:10:08 darkdemonserver -- MARK --
Mar 2 05:30:08 darkdemonserver -- MARK --
Mar 2 05:50:08 darkdemonserver -- MARK --
Mar 2 06:10:08 darkdemonserver -- MARK --
Mar 2 06:25:15 darkdemonserver syslogd 1.4.1#17: restart.
 
jlasman said:
Those messages have nothing to do with BIND.

Jeff
Click to expand...
I know, but that's the only thing it shows.

Also, via DA it should be possible to restart the named server, but none of the services can be restarted or so...

Maybe if someone wants to look at my server personally... i really hate these errors...
 
alloin said:
I know, but that's the only thing it shows.
Click to expand...
There aren't any darkdemonserver entries in google, so I'm guessing it's something local to your server.
Also, via DA it should be possible to restart the named server, but none of the services can be restarted or so...
Click to expand...
Services can be restarted using the Service Monitor from the admin control panel.

Jeff
 
jlasman said:

Services can be restarted using the Service Monitor from the admin control panel.

Jeff
Click to expand...
I know, but it doesn't when i click on reload... how to fix this ?
 
I can't say because we don't know what's wrong.

First try restart instead of reload.

If that doesn't work:

Shell in as root, run a restart command and see if you get errors.

How you do that depends on your OS Distribution.

If you get errors or it doesn't restart, then tail the error log while you're restarting the service, to see any errors it gives.

Jeff
 
You must log in or register to reply here.
Back
Top