Go_Big_Blue
February 5th, 2009, 04:43 PM
I have been following the www.howtoforge.com website for setting up NAT, iptables, port forwarding, DNS and DHCP. (http://www.howtoforge.com/nat-gateway-iptables-port-forwarding-dns-and-dhcp-setup-ubuntu-8.10-server)
About half-way through this whole setup up (at the point where it says to do a 'nslookup macpro') things start to get a little squirrely - actually a whole lot of squirrely!!!
For example,
I typed in hostname -f at the command line and it returned: 'AOPserver1.AOP1.com'
So then I typed in the following:
root@AOPserver1:/etc/bind/zones# nslookup 10.4.16.4
Server: 205.152.37.23
Address: 205.152.37.23#53
** server can't find 4.16.4.10.in-addr.arpa.: NXDOMAIN
root@AOPserver1:/etc/bind/zones# nslookup macpro
Server: 205.152.37.23
Address: 205.152.37.23#53
** server can't find macpro: NXDOMAIN
root@AOPserver1:/etc/bind/zones# cd
root@AOPserver1:~# host server
Host server not found: 3(NXDOMAIN)
root@AOPserver1:~# host 192.168.1.1
Host 1.1.168.192.in-addr.arpa. not found: 3(NXDOMAIN)
root@AOPserver1:~# host aop1.com
Host aop1.com not found: 3(NXDOMAIN)
root@AOPserver1:~# nslookup server
Server: 205.152.37.23
Address: 205.152.37.23#53
** server can't find server: NXDOMAIN
root@AOPserver1:~# nslookup 192.168.1.1
Server: 205.152.37.23
Address: 205.152.37.23#53
** server can't find 1.1.168.192.in-addr.arpa.: NXDOMAIN
So then I found on a forum on the web that I could try to edit the /etc/resolv.conf file. So I did, and then I got the following:
root@AOPserver1:~# pico /etc/resolv.conf (this is where I edited the file)
root@AOPserver1:~# nslookup 10.4.16.4
Server: 10.4.16.42
Address: 10.4.16.42#53
4.16.4.10.in-addr.arpa name = macpro.AOP1.com.
root@AOPserver1:~# nslookup 10.4.16.4
Server: 10.4.16.42
Address: 10.4.16.42#53
4.16.4.10.in-addr.arpa name = macpro.AOP1.com.
root@AOPserver1:~# nslookup macpro
Server: 10.4.16.42
Address: 10.4.16.42#53
Name: macpro.AOP1.com
Address: 10.4.16.4
So at this point my level of frustration is down (but only for a little while as we shall soon see). So then I continue to follow the guide from www.howtoforge.com. It says to run the command 'named' to start named. So I enter the following:
root@AOPserver1:~# sudo /etc/init.d/named start
sudo: /etc/init.d/named: command not found
Then the tutorial says that if it doesn't start to check the /var/logs. Okay - well the dang thing doesn't exist, so there is nothing in the /var/logs to check!!!! But funny thing is ... earlier in the tutorial they had you edit the file /etc/bind/named.conf.
I am extremely frustrated at this point and ready to call off this whole setup!!! Ubuntu prides itself on being user friendly, but I find it to be more user frustrating than anything.
Would one of you kind-hearted and intelligent individuals out there please help me get this problem fixed? Thanking you in advance.
About half-way through this whole setup up (at the point where it says to do a 'nslookup macpro') things start to get a little squirrely - actually a whole lot of squirrely!!!
For example,
I typed in hostname -f at the command line and it returned: 'AOPserver1.AOP1.com'
So then I typed in the following:
root@AOPserver1:/etc/bind/zones# nslookup 10.4.16.4
Server: 205.152.37.23
Address: 205.152.37.23#53
** server can't find 4.16.4.10.in-addr.arpa.: NXDOMAIN
root@AOPserver1:/etc/bind/zones# nslookup macpro
Server: 205.152.37.23
Address: 205.152.37.23#53
** server can't find macpro: NXDOMAIN
root@AOPserver1:/etc/bind/zones# cd
root@AOPserver1:~# host server
Host server not found: 3(NXDOMAIN)
root@AOPserver1:~# host 192.168.1.1
Host 1.1.168.192.in-addr.arpa. not found: 3(NXDOMAIN)
root@AOPserver1:~# host aop1.com
Host aop1.com not found: 3(NXDOMAIN)
root@AOPserver1:~# nslookup server
Server: 205.152.37.23
Address: 205.152.37.23#53
** server can't find server: NXDOMAIN
root@AOPserver1:~# nslookup 192.168.1.1
Server: 205.152.37.23
Address: 205.152.37.23#53
** server can't find 1.1.168.192.in-addr.arpa.: NXDOMAIN
So then I found on a forum on the web that I could try to edit the /etc/resolv.conf file. So I did, and then I got the following:
root@AOPserver1:~# pico /etc/resolv.conf (this is where I edited the file)
root@AOPserver1:~# nslookup 10.4.16.4
Server: 10.4.16.42
Address: 10.4.16.42#53
4.16.4.10.in-addr.arpa name = macpro.AOP1.com.
root@AOPserver1:~# nslookup 10.4.16.4
Server: 10.4.16.42
Address: 10.4.16.42#53
4.16.4.10.in-addr.arpa name = macpro.AOP1.com.
root@AOPserver1:~# nslookup macpro
Server: 10.4.16.42
Address: 10.4.16.42#53
Name: macpro.AOP1.com
Address: 10.4.16.4
So at this point my level of frustration is down (but only for a little while as we shall soon see). So then I continue to follow the guide from www.howtoforge.com. It says to run the command 'named' to start named. So I enter the following:
root@AOPserver1:~# sudo /etc/init.d/named start
sudo: /etc/init.d/named: command not found
Then the tutorial says that if it doesn't start to check the /var/logs. Okay - well the dang thing doesn't exist, so there is nothing in the /var/logs to check!!!! But funny thing is ... earlier in the tutorial they had you edit the file /etc/bind/named.conf.
I am extremely frustrated at this point and ready to call off this whole setup!!! Ubuntu prides itself on being user friendly, but I find it to be more user frustrating than anything.
Would one of you kind-hearted and intelligent individuals out there please help me get this problem fixed? Thanking you in advance.