|
|
|
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
#1
|
|||
|
|||
|
Bind issuse www.mx.com not resolving...BUT
for some odd reason www.mx.com is not resolving but dex.mx.com does and ns1.mx.com and ns2.mx.com resolve fine... any ideas....
I'm running bind 9.2 or what ever the latest verision is on a slackware 10.0 box..... // mx named.conf options { directory "/var/named"; }; zone "0.0.127.in-addr.arpa" { type master; file "0.0.127.in-addr.arpa.zone"; }; zone "1.1.10.in-addr.arpa" { type master; file "1.1.10.in-addr.arpa.zone"; }; zone "100.100.100.in-addr.arpa" { type master; file "100.100.100.in-addr.arpa.zone"; }; zone "localhost" { type master; file "localhost.zone"; }; zone "mx.com" { type master; file "mx.com.zone"; }; include "/etc/rndc.key"; ///////////////////////////////////////////////// // mx.com.zone $TTL 86400 @ IN SOA ns1.mx.com. root.mx.com. ( 2003091104 28800 7200 604800 86400 ) @ IN NS ns1.mx.com. @ IN NS ns2.mx.com. @ IN MX 5 mail.mx.com. @ IN A 100.100.100.001 mail IN A 100.100.100.001 ftp IN A 100.100.100.001 mxdev.mx.com. IN A 100.100.100.001 ///////////////////////////////////////////////////// // 0.0.127.in-addr.arpa.zone $TTL 86400 @ IN SOA ns1.mx.com. root.mx.com. ( 1 ; serial 28800 ; refresh 7200 ; retry 604800 ; expire 86400 ; ttk ) @ IN NS ns1.mx.com. @ IN NS ns2.mx.com. 1 IN PTR localhost. /////////////////////////////////////////////////////// // 1.1.10.in-addr.arpa.zone $TTL 86400 @ IN SOA ns1.mx.com. root.mx.com. ( 2003091101 ; serial 28800 ; refresh 7200 ; retry 604800 ; expire 86400 ; ttk ) @ IN NS ns1.mx.com. @ IN NS ns2.mx.com. @ IN MX 5 mail.mx.com. 66 IN PTR localhost. 2 IN PTR subdomain.mx.com. //////////////////////////////////// //100.100.100.in-addr.arpa.zone $TTL 86400 @ IN SOA ns1.mx. root.localhost ( 4 28800 7200 604800 86400 ) @ IN NS ns1.mx.com. @ IN NS ns2.mx.com. 66 IN PTR mx.com. 001.100.100.100.in-addr.arpa. IN PTR mxdev.mx.com. the mx.com is not the actual dot com I'm trying to get working ... just a short down verision of the actual dot com and the ip 100.100.100.001 of course isnt valid I just replace the vaild IP of my server with that to show my config files with out releasing the info of my dot com that is almost working if I could just figure out why www.mx.com doesnt work..... any help would be great.......... back to researching.... [sd] |
|
#2
|
||||
|
||||
|
Quote:
Kinda makes sense that "www" doesn't resolve considering you haven't assigned it an IP address.
__________________
Send me a private message if you would like me to setup your DNS for you for a price of your choosing. This is the preferred method if your DNS needs to be fixed/setup fast and you don't have the time to bounce messages back and forth on a forum. Also, check out these links: Whois Direct | DNS Crawler | NS Trace | Compare Free DNS Hosts |
|
#3
|
|||
|
|||
|
like this
www IN A 100.100.100.001 ????? |
|
#4
|
||||
|
||||
|
have you tried it, does it work?
|
|
#5
|
|||
|
|||
|
tried it still doesnt work
![]() |
|
#6
|
||||
|
||||
|
is mx the real domain? I'm trying to test it.
|
|
#7
|
|||
|
|||
|
nope the real domain is mtothex.com ..... ns1.mtothex.com resolves but not www.mtothex.com
|
|
#8
|
||||
|
||||
|
let me see the results of this command:
named -u named -g Last edited by SilentRage : July 23rd, 2004 at 10:14 AM. |
|
#9
|
|||
|
|||
|
root@mxdev:~# named -u named -g
Jul 26 15:58:20.717 starting BIND 9.2.3 -u named -g Jul 26 15:58:20.731 using 1 CPU Jul 26 15:58:20.736 loading configuration from '/etc/named.conf' Jul 26 15:58:20.762 no IPv6 interfaces found Jul 26 15:58:20.762 listening on IPv4 interface lo, 127.0.0.1#53 Jul 26 15:58:20.763 binding TCP socket: address in use Jul 26 15:58:20.763 listening on IPv4 interface eth0, 192.168.10.100#53 Jul 26 15:58:20.763 binding TCP socket: address in use Jul 26 15:58:20.766 couldn't add command channel 127.0.0.1#953: address in use Jul 26 15:58:20.766 ignoring config file logging statement due to -g option Jul 26 15:58:20.766 couldn't open pid file '/var/run/named/named.pid': File exists Jul 26 15:58:20.766 exiting (due to early fatal error) |
|
#10
|
||||
|
||||
|
ok run these commands in sequence. The first stops the server, the next gets startup information (paste results again), the next starts the server.
killall -KILL named named -u named -g named -u named |
|
#11
|
|||
|
|||
|
root@mxdev:~# killall -KILL named
root@mxdev:~# named -u named -g Jul 27 13:29:20.129 starting BIND 9.2.3 -u named -g Jul 27 13:29:20.129 using 1 CPU Jul 27 13:29:20.135 loading configuration from '/etc/named.conf' Jul 27 13:29:20.161 no IPv6 interfaces found Jul 27 13:29:20.162 listening on IPv4 interface lo, 127.0.0.1#53 Jul 27 13:29:20.163 listening on IPv4 interface eth0, 192.168.10.100#53 Jul 27 13:29:20.165 command channel listening on 127.0.0.1#953 Jul 27 13:29:20.165 ignoring config file logging statement due to -g option Jul 27 13:29:20.165 couldn't open pid file '/var/run/named/named.pid': File exists Jul 27 13:29:20.165 exiting (due to early fatal error) root@mxdev:~# named -u named |
|
#12
|
||||
|
||||
|
damn, let's try this again.
killall -KILL named rm -rf /var/run/named/named.pid named -u named -g named -u named |
|
#13
|
|||
|
|||
|
Lowery's Law:
If it jams -- force it. If it breaks, it needed replacing anyway. root@mxdev:~# killall -KILL named root@mxdev:~# rm -rf /var/run/named/named.pid root@mxdev:~# named -u named -g Jul 29 19:04:20.842 starting BIND 9.2.3 -u named -g Jul 29 19:04:20.845 using 1 CPU Jul 29 19:04:20.850 loading configuration from '/etc/named.conf' Jul 29 19:04:20.876 no IPv6 interfaces found Jul 29 19:04:20.877 listening on IPv4 interface lo, 127.0.0.1#53 Jul 29 19:04:20.878 listening on IPv4 interface eth0, 192.168.10.100#53 Jul 29 19:04:20.880 command channel listening on 127.0.0.1#953 Jul 29 19:04:20.880 ignoring config file logging statement due to -g option Jul 29 19:04:20.880 couldn't open pid file '/var/run/named/named.pid': Permission denied Jul 29 19:04:20.881 exiting (due to early fatal error) root@mxdev:~# named -u named root@mxdev:~# thanks for the help by the way... ![]() |
|
#14
|
||||
|
||||
|
excellent, we've made progress. Now to polish it up.
killall -KILL named rm -rf /var/run/named/named.pid chmod 777 /var chmod 777 /var/run chmod 777 /var/run/named chown -R named:named /var/run/named named -u named -g named -u named At this point your server should be running smoothly. |
|
#15
|
|||
|
|||
|
almost ... I think... its hanging on the 2nd to last command......
root@mxdev:~# named -u named -g Jul 31 12:42:35.374 starting BIND 9.2.3 -u named -g Jul 31 12:42:35.374 using 1 CPU Jul 31 12:42:35.379 loading configuration from '/etc/named.conf' Jul 31 12:42:35.398 no IPv6 interfaces found Jul 31 12:42:35.399 listening on IPv4 interface lo, 127.0.0.1#53 Jul 31 12:42:35.400 listening on IPv4 interface eth0, 192.168.10.100#53 Jul 31 12:42:35.403 command channel listening on 127.0.0.1#953 Jul 31 12:42:35.404 ignoring config file logging statement due to -g option Jul 31 12:42:35.407 zone 1.1.10.in-addr.arpa/IN: loaded serial 2003091101 Jul 31 12:42:35.411 dns_rdata_fromtext: 0.0.127.in-addr.arpa.zone:3: near eol: unexpected end of input Jul 31 12:42:35.411 zone 0.0.127.in-addr.arpa/IN: loading master file 0.0.127.in-addr.arpa.zone: unexpected end of input Jul 31 12:42:35.412 zone 244.93.66.in-addr.arpa/IN: loaded serial 4 Jul 31 12:42:35.413 dns_rdata_fromtext: mtothex.com.zone:2: near 'www.mtothex.com.': not a valid number Jul 31 12:42:35.413 zone mtothex.com/IN: loading master file mtothex.com.zone: not a valid number Jul 31 12:42:35.414 zone localhost/IN: loaded serial 1 Jul 31 12:42:35.414 running Jul 31 12:42:35.414 zone 1.1.10.in-addr.arpa/IN: sending notifies (serial 2003091101) Jul 31 12:42:35.415 zone 244.93.66.in-addr.arpa/IN: sending notifies (serial 4) |