Nameservers questions / help

The ks*******.kimsufi.com is my servers name “System hostname ks*****.kimsufi.com”
also its where i log into webmin

Replace the kimsufi thingy in the SOA and the NS record with “ns1.vodkaholic.co.uk.” and try again.

(And tomorrow, you need to pay for the alcohol withdrawal treatment that I’ll require. :wink: )

Haha dam am skint as it is :frowning:

oki i changed that to


$ttl 38400
@	IN	SOA	ns1.vodkaholic.co.uk. root.ns1.vodkaholic.co.uk. (
			1289399469
			10800
			3600
			604800
			38400 )
@	IN	NS	ns1.vodkaholic.co.uk.
vodkaholic.co.uk.	IN	A	188.165.217.101
www.vodkaholic.co.uk.	IN	A	188.165.217.101
ftp.vodkaholic.co.uk.	IN	A	188.165.217.101
m.vodkaholic.co.uk.	IN	A	188.165.217.101
localhost.vodkaholic.co.uk.	IN	A	127.0.0.1
webmail.vodkaholic.co.uk.	IN	A	188.165.217.101
admin.vodkaholic.co.uk.	IN	A	188.165.217.101
mail.vodkaholic.co.uk.	IN	A	188.165.217.101
vodkaholic.co.uk.	IN	MX	5 mail.vodkaholic.co.uk.
vodkaholic.co.uk.	IN	TXT	"v=spf1 a mx a:vodkaholic.co.uk ip4:188.165.217.101 ?all"
ns1.vodkaholic.co.uk.	IN	A	188.165.217.101
ns2.vodkaholic.co.uk.	IN	A	188.165.217.101

restarted BIND and is the same as before (unless i edited it wrong)
Thanks

You need to increment the serial number (the 128939…) each time you make a change to the zone, otherwise it won’t be recognized as changed.

Oh now WAIT. I just noticed something in your syslog.

Nov 11 01:33:11 ks312361 named[8788]: running Nov 11 01:33:47 ks312361 pdns[20553]: Not authoritative for 'vodkaholic.co.uk', sending servfail to 92.114.98.140 (recursion was desired)

Take a close look at the application tags. You are running two nameservers (BIND and PowerDNS) on your system! No wonder BIND says that port 53 is in use. And it’s PowerDNS who’s replying SERVFAIL to the queries.

You might want to fix that first before trying anything else. :stuck_out_tongue_winking_eye: (The old saying two are better than one does not apply in all cases.)

Hmm am not sure how lol i did “aptitude purge pdns-recursor” thats all i could find now do i know if its gone sorry for the lame question ;/

Well, the most feasible way is probably to restart BIND and check the syslog if it’s still complaining about being unable to use port 53. :slight_smile:

Ok looks like i did it (got rid of powerdns that is)

Nov 11 03:08:56 ks312361 named[17582]: shutting down Nov 11 03:08:56 ks312361 named[17582]: stopping command channel on 127.0.0.1#953 Nov 11 03:08:56 ks312361 named[17582]: stopping command channel on ::1#953 Nov 11 03:08:56 ks312361 named[17582]: no longer listening on 127.0.0.1#53 Nov 11 03:08:56 ks312361 named[17582]: no longer listening on ::1#53 Nov 11 03:08:56 ks312361 named[17582]: exiting Nov 11 03:08:56 ks312361 named[18034]: starting BIND 9.6-ESV-R1 -c /etc/bind/named.conf Nov 11 03:08:56 ks312361 named[18034]: built with '--prefix=/usr' '--build=x86_64-linux-gnu' '--host=x86_64-linux-gnu' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--sysconfdir=/etc/bind' '--localstatedir=/var/run/bind' '--enable-threads' '--enable-largefile' '--with-libtool' '--enable-shared' '--enable-static' '--with-openssl=/usr' '--with-gssapi=/usr' '--with-gnu-ld' '--with-dlz-postgres=no' '--with-dlz-mysql=no' '--with-dlz-bdb=yes' '--with-dlz-filesystem=yes' '--with-dlz-ldap=yes' '--with-dlz-stub=yes' '--enable-ipv6' 'build_alias=x86_64-linux-gnu' 'host_alias=x86_64-linux-gnu' 'CFLAGS=-fno-strict-aliasing -DDIG_SIGCHASE -DNS_RUN_PID_DIR=0 -O2' 'LDFLAGS=' 'CPPFLAGS=' 'CXXFLAGS=-g -O2' 'FFLAGS=-g -O2' Nov 11 03:08:56 ks312361 named[18034]: adjusted limit on open files from 1024 to 1048576 Nov 11 03:08:56 ks312361 named[18034]: found 8 CPUs, using 8 worker threads Nov 11 03:08:56 ks312361 named[18034]: using up to 4096 sockets Nov 11 03:08:56 ks312361 named[18034]: loading configuration from '/etc/bind/named.conf' Nov 11 03:08:56 ks312361 named[18034]: using default UDP/IPv4 port range: [1024, 65535] Nov 11 03:08:56 ks312361 named[18034]: using default UDP/IPv6 port range: [1024, 65535] Nov 11 03:08:56 ks312361 named[18034]: listening on IPv4 interface lo, 127.0.0.1#53 Nov 11 03:08:56 ks312361 named[18034]: listening on IPv6 interface lo, ::1#53 Nov 11 03:08:56 ks312361 named[18034]: automatic empty zone: 254.169.IN-ADDR.ARPA Nov 11 03:08:56 ks312361 named[18034]: automatic empty zone: 2.0.192.IN-ADDR.ARPA Nov 11 03:08:56 ks312361 named[18034]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA Nov 11 03:08:56 ks312361 named[18034]: automatic empty zone: 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA Nov 11 03:08:56 ks312361 named[18034]: automatic empty zone: 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA Nov 11 03:08:56 ks312361 named[18034]: automatic empty zone: D.F.IP6.ARPA Nov 11 03:08:56 ks312361 named[18034]: automatic empty zone: 8.E.F.IP6.ARPA Nov 11 03:08:56 ks312361 named[18034]: automatic empty zone: 9.E.F.IP6.ARPA Nov 11 03:08:56 ks312361 named[18034]: automatic empty zone: A.E.F.IP6.ARPA Nov 11 03:08:56 ks312361 named[18034]: automatic empty zone: B.E.F.IP6.ARPA Nov 11 03:08:56 ks312361 named[18034]: command channel listening on 127.0.0.1#953 Nov 11 03:08:56 ks312361 named[18034]: command channel listening on ::1#953 Nov 11 03:08:56 ks312361 named[18034]: zone 0.in-addr.arpa/IN: loaded serial 1 Nov 11 03:08:56 ks312361 named[18034]: zone 127.in-addr.arpa/IN: loaded serial 1 Nov 11 03:08:56 ks312361 named[18034]: zone 255.in-addr.arpa/IN: loaded serial 1 Nov 11 03:08:56 ks312361 named[18034]: zone babylon5rpg.com/IN: loaded serial 1289353370 Nov 11 03:08:56 ks312361 named[18034]: zone myanimeisland.com/IN: loaded serial 1289365276 Nov 11 03:08:56 ks312361 named[18034]: zone rpg-central.com/IN: loaded serial 1289352156 Nov 11 03:08:56 ks312361 named[18034]: zone stargatecommandrpg.com/IN: loaded serial 1289357904 Nov 11 03:08:56 ks312361 named[18034]: zone localhost/IN: loaded serial 2 Nov 11 03:08:56 ks312361 named[18034]: zone vodkaholic.co.uk/IN: loaded serial 1289399469 Nov 11 03:08:56 ks312361 named[18034]: running Nov 11 03:09:01 ks312361 /USR/SBIN/CRON[18059]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -type f -cmin +$(/usr/lib/php5/maxlifetime) -print0 | xargs -n 200 -r -0 rm) Nov 11 03:09:01 ks312361 /USR/SBIN/CRON[18060]: (root) CMD (/usr/local/rtm/bin/rtm 24 > /dev/null 2> /dev/null)

Nov 11 03:08:56 ks312361 named[18034]: listening on IPv4 interface lo, 127.0.0.1#53

Now you need to configure BIND to listen on 0.0.0.0 instead.

And it’s not really intended to have two nameservers point to the same IP address… It’s meant for redundancy. :slight_smile:

Good luck for now, need to continue tomorrow, bedtime here.

0.0.0.0 ?and thanks for the help :slight_smile:

Edit =

http://www.intodns.com/vodkaholic.co.uk
seem to work now O_o

0.0.0.0 as opposed to specifying a concrete IP means “listen on all interfaces”.

Yes, your domain resolves correctly from the outside now.

How can i set it all to 0.0.0.0
also is everything working ok now i still see alot of errors on intodns.com page

Thanks again

Setting to “listen on all”: Go to Webmin -> Servers -> BIND DNS Server -> Addresses and Topology and set “Ports and addresses to listen on” to “Default”. That should remove any LISTEN directives from the config, and the default is to listen on all interfaces.

Checking out that “intodns” thingy in a bit.

Mmh, this “intodns” thingy is nice. :slight_smile: Need to put that in my bookmarks. I usually use the “nameserver predelegation check” web interface from DENIC.

It seems that right now your BIND is down again (or a firewall blocking port 53), since I cannot dig from it.

Ok i changed the above and restarted

Hmm seems pdns is still here my logs are full of this

Nov 11 18:22:54 ks312361 pdns[5473]: Our pdns instance exited with code 1 Nov 11 18:22:54 ks312361 pdns[5473]: Respawning Nov 11 18:22:55 ks312361 pdns[7153]: Guardian is launching an instance Nov 11 18:22:55 ks312361 pdns[7153]: This is module gmysqlbackend.so reporting Nov 11 18:22:55 ks312361 pdns[7153]: This is a guarded instance of pdns Nov 11 18:22:55 ks312361 pdns[7153]: It is advised to bind to explicit addresses with the --local-address option Nov 11 18:22:55 ks312361 pdns[7153]: binding UDP socket to '0.0.0.0': Address already in use Nov 11 18:22:55 ks312361 pdns[7153]: Fatal error: Unable to bind to UDP socket Nov 11 18:22:56 ks312361 pdns[5473]: Our pdns instance exited with code 1 Nov 11 18:22:56 ks312361 pdns[5473]: Respawning Nov 11 18:22:57 ks312361 pdns[7154]: Guardian is launching an instance Nov 11 18:22:57 ks312361 pdns[7154]: This is module gmysqlbackend.so reporting Nov 11 18:22:57 ks312361 pdns[7154]: This is a guarded instance of pdns Nov 11 18:22:57 ks312361 pdns[7154]: It is advised to bind to explicit addresses with the --local-address option Nov 11 18:22:57 ks312361 pdns[7154]: binding UDP socket to '0.0.0.0': Address already in use Nov 11 18:22:57 ks312361 pdns[7154]: Fatal error: Unable to bind to UDP socket Nov 11 18:22:58 ks312361 pdns[5473]: Our pdns instance exited with code 1 Nov 11 18:22:58 ks312361 pdns[5473]: Respawning Nov 11 18:22:59 ks312361 pdns[7155]: Guardian is launching an instance Nov 11 18:22:59 ks312361 pdns[7155]: This is module gmysqlbackend.so reporting Nov 11 18:22:59 ks312361 pdns[7155]: This is a guarded instance of pdns Nov 11 18:22:59 ks312361 pdns[7155]: It is advised to bind to explicit addresses with the --local-address option Nov 11 18:22:59 ks312361 pdns[7155]: binding UDP socket to '0.0.0.0': Address already in use Nov 11 18:22:59 ks312361 pdns[7155]: Fatal error: Unable to bind to UDP socket Nov 11 18:23:00 ks312361 pdns[5473]: Our pdns instance exited with code 1 Nov 11 18:23:00 ks312361 pdns[5473]: Respawning Nov 11 18:23:01 ks312361 pdns[7156]: Guardian is launching an instance Nov 11 18:23:01 ks312361 pdns[7156]: This is module gmysqlbackend.so reporting Nov 11 18:23:01 ks312361 pdns[7156]: This is a guarded instance of pdns Nov 11 18:23:01 ks312361 pdns[7156]: It is advised to bind to explicit addresses with the --local-address option Nov 11 18:23:01 ks312361 pdns[7156]: binding UDP socket to '0.0.0.0': Address already in use Nov 11 18:23:01 ks312361 pdns[7156]: Fatal error: Unable to bind to UDP socket

Quite obviously so. How did you install this system if I may ask, that you ended up with two nameservers? You probably did not use the Virtualmin install script, did you?

What distro is this? You should check your package manager (aptitude for Ubuntu/Debian) for anything pdns related and nuke it. :slight_smile:

Hey yes i used the Virtualmin install script as i could get Bind to work i tryed power dns. As am a noob i followed this post http://www.howtoforge.com/installing-powerdns-with-mysql-backend-and-poweradmin-on-debian-etch

I run Debian Lenny

Yikes… yeah, those nice tutorials. They sure basically work, but probably don’t take into account what stuff is already on your system. :slight_smile: Now try to get rid of all that PDNS stuff again, and we shall see.

Any ideas on how to get rid of it mate :frowning:

See my previous post. :slight_smile:

EDIT: Oh, wait you wrote your distro there. Okay Lenny should have aptitude. Start it, and use the search function (press “/”, then enter a regular expression of package name to look for) to check for any installed powerdns related packages.