dns <> ping problem

[freakie]

Hi,

When i ping to non-existent domains my own server still responds.

/etc/resolv.conf:

search itens.net
nameserver 127.0.0.1
nameserver 83.137.18.35
nameserver 83.137.18.36
nameserver 83.137.17.11
nameserver 83.137.17.12
nameserver 83.137.20.11
nameserver 83.137.20.12
nameserver 83.137.20.10
nameserver 83.137.17.10


How is that possible ?

 

[nobaloney]

The first server checked is 127.0.0.1; your local server.

I don't know your IP# so I can't check it.

Jeff

 

[freakie]

the first is the local, the second and the third is the da server itself.

 

[nobaloney]

Your server responds because it's acting as a cacheing nameserver and it's first in the list.

Jeff

 

[freakie]

Perhaps a dumb question

but how do i do change that, i've tried several configuration options.

im using centos 4.6

freakie / stefan

 

[nobaloney]

How do you change what? Do you want to make it a non-cacheing nameserver? Or just remove it from the list?

Jeff

 

[freakie]

well,

locally it should resolve any domain, ons the outside it should only resolve domains registered in DA.

But the fact that it responds to ping commands on any domain, even non-existing ones is quite crappy if you ask me.

that is waht it should do.

 

[nobaloney]

DirectAdmin doesn't know what you want it to do, so DirectAdmin doesn't make the decision for you.

Generally when you set up a server for DirectAdmin you install your distribution's BIND packages. On many distributions you can chose whether or not you want a caching nameserver. On Red Hat/CentOS distributions first you'd install the bind rpm and then the caching-nameserver rpm. The first thing to do is to save your named.conf file. The next thing to do is to remove your caching-nameserver rpm Then check to make sure you've still got all your domains listed in named.conf, and if not, copy in the missing section from your backup. Check to see if your system created a named.conf file with an .rpm ending, and make sure the caching nameserver line isn't included in the options section of your named.conf file (check it against your backup).

Then add this line somewhere in the options section of your named.conf file:

allow-recursion { 127.0.0.1; };

That should work.

Note, however that it's not a perfect solution; one limitation of how BIND is implemented is that once you've done an internal lookup and that domain name is in the cache, your nameserver WILL serve requests for that domain from the cache.

Jeff