PDA

View Full Version : Fresh install with DNS issues


bullium
31st March 2009, 03:06
I've got a fresh install of ISPConfig 3.0.1 on Ubunutu Server 8.04.2, but I'm having some issues with DNS and would like some pointers on how to fix my problem :).

I used the following thread (http://www.howtoforge.com/mydns_mydnsconfig_dnsmasp_on_ubuntu_edgy) and used the last step "Installing DNSMasq" to allow mydns to use dnsmasq as a local resolver, so I could use dig for troubleshooting.

I have a local client machine 192.168.1.101 that points to the ISPConfig servers IP address 192.168.1.100 for DNS., but the
system will not resolve the dns names as they are input into ISPConfig's DNS records page. Below are screenshots of my ISPConfig config screens, as well as screenshots from dig output as it's ran on the server (see servers /etc/resolv.conf entries below) and mydnsexport. I know the web servers and such are answering properly as I get a "Welcome to your website!" when I plug in the servers IP address into the address bar. Also, I might add at the moment I am only trying to get this working locally for testing purposes.

Servers /etc/resolv.conf
nameserver 127.0.0.1
nameserver 192.168.1.100
nameserver 192.168.1.1


mydnsexport output

root@usrv:~# mydnsexport
$TTL 86400
; Zone: testinc.com. (#3)
; Created by "mydnsexport"
; Mon Mar 30 20:54:47 2009
$ORIGIN testinc.com.

@ IN SOA ns1.testinc.com. webmaster.testinc.com. (
2009033001 ; Serial
28800 ; Refresh
7200 ; Retry
604800 ; Expire
86400 ) ; Minimum

ns1.testinc.com 86400 IN A 192.168.1.100
ns2.testinc.com 86400 IN A 192.168.1.100
testinc.com 86400 IN A 192.168.1.100
testinc.com 86400 IN MX 10 mx.testinc.com.
testinc.com 86400 IN NS ns1.testinc.com.
testinc.com 86400 IN NS ns2.testinc.com.
www.testinc.com 86400 IN A 192.168.1.100


mydns, dnsmasq and all other services are running per netstat.
root@usrv:~# netstat -tap
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
PID/Program name
tcp 0 0 localhost:10024 *:* LISTEN
4897/amavisd (maste
tcp 0 0 localhost:10025 *:* LISTEN
5525/master
tcp 0 0 localhost:mysql *:* LISTEN
4971/mysqld
tcp 0 0 localhost:spamd *:* LISTEN
5033/spamd.pid
tcp 0 0 *:webcache *:* LISTEN
5652/apache2
tcp 0 0 *:www *:* LISTEN
5652/apache2
tcp 0 0 192.168.1.100:domain *:* LISTEN
6638/mydns
tcp 0 0 *:ftp *:* LISTEN
5538/pure-ftpd (SER
tcp 0 0 localhost:domain *:* LISTEN
4843/dnsmasq
tcp 0 0 *:smtp *:* LISTEN
5525/master
tcp 0 0 *:https *:* LISTEN
5652/apache2
tcp6 0 0 [::]:imaps [::]:* LISTEN
5422/couriertcpd
tcp6 0 0 [::]:pop3s [::]:* LISTEN
5456/couriertcpd
tcp6 0 0 [::]:pop3 [::]:* LISTEN
5436/couriertcpd
tcp6 0 0 [::]:imap2 [::]:* LISTEN


Any help would be greatly appreciated. If you need anymore info to help troubleshoot just let me know. Thanks.

till
31st March 2009, 08:52
You missed the dots at the end of the domain names in all of your records. For example, it must be:

testinc.com. 86400 IN A 192.168.1.100

and not:

testinc.com 86400 IN A 192.168.1.100

use the dns wizard to craete a new record to get an example how it is setup correctly.

bullium
31st March 2009, 10:20
You missed the dots at the end of the domain names in all of your records. For example, it must be:

testinc.com. 86400 IN A 192.168.1.100

and not:

testinc.com 86400 IN A 192.168.1.100

use the dns wizard to craete a new record to get an example how it is setup correctly.

I knew it was going to be something very simple. It's working great now thanks for the help till.