Reverse DNS problem Post: 302229400

9 More Discussions You Might Find Interesting

1. IP Networking

reverse lookup file problem

I'm trying to create a reverse lookup file. Below are the error messages I get in the messages file, when I start named. Below the error messages is a copy of the reverse lookup file I'm trying to use. I'm using Bind version 8.1.2. Would someone recommend the correct values and if you see any...

2. UNIX for Dummies Questions & Answers

telnet refused / reverse DNS issue?

I have users with laptops who may telnet from the local network one minute and then connect remotely a short time later from a different IP address. This causes a problem as the UnixWare 7.1.1 server appears to try to resolve the remote machine name (via our primary DNS server) to the IP...

3. UNIX for Advanced & Expert Users

[DNS] Reverse Lookup for 2 IP Addresses

Originally I had the server at home and on Comcast so I used dyndns.org for DNS. Once the server got a bit more popular, I leased a server at a colo facility. They set up the server name in their DNS so I didn't really have any reason to manage my own DNS. DynDNS was managing the domains and I...

4. UNIX for Advanced & Expert Users

dnsstuff says no reverse dns in place, but there is!

Folks...have just stumbled on an issue where DNSstuff says there is no reverse dns in place when there is...as evidenced by a reverse check from 3 diff networks. Any advice why this would be happening (DNSstuff-wise) would be appreciated. Jordan: jsd@standby:~$ host 12.177.133.70...

5. UNIX for Dummies Questions & Answers

DNS forward and reverse entry required thorugh scripting instead of manually done

HI GUrus, I am very mcuh new for this forum ....i need you all guys help for resolving my queries. As i have DNS server , platform is sunsolaris----8. We are using that serevr for resolving all network nodes. I am going to explain the process what i am following .... I could have...

6. Red Hat

Mail Problem. Maybe, it is a DNS Problem!

Hi, i've a redhat linux 9 upadated by redhat from 7 version to 9 version. A couple of days ago i was a problem with my mail, in other words i'm not able to get any email nor to send any email. I've a proxy configuration and i tried to set iptables in order to verify the port. The 110,255 and 995...

7. IP Networking

Reverse DNS

Hello, I'm trying to get reverse dns to point to my domain on network but I'm failing. I am using bind dns with port 53 enabled and my ISP is mediacom. Currently my reverse dns is *.client.mchsi.com and I would like to make it example.com basically. My bind configuration I have 2 records, one...

8. IP Networking

HOWTO: Linux multihomed dns client - reverse lookup

The following thread is closed: 133552-howto-linux-multihomed-dns-client (Sorry I am not allowed to post URLs) Therefore I write this append in an own thread. The HOWTO in the referenced thread helped me a lot and I only want to append how to make reverse lookup working for a local zone: ...

9. Red Hat

DNS reverse lookup issue

Hi guys. Ok so let me lay out my configs. I can do a NSlookup from client to server BUT NOT a reverse lookup. DNS server: Optimus.jaydomain.com IP : 192.168.1.50 DNS Client: Megatron.jaydomain.com IP : 192.168.1.60 On Sever: # cat /etc/named.conf // // named.conf // // Provided...

LEARN ABOUT DEBIAN

desproxy-dns

desproxy-dns(1) 						   User Commands						   desproxy-dns(1)

NAME

       desproxy-dns - DNS for dynamic connections

SYNOPSIS

	  desproxy-dns dns_server proxy_host proxy_port

OPTIONS

       None

DESCRIPTION

       If you have direct DNS access then you don't need to do anything else.  You know you have direct DNS access if you can resolve host names
       to IP addresses.

       NOTE: as desproxy-dns listens in port 53 (which is less than 1024) you may need administrator privileges to exec desproxy-dns (in fact if
       you are running UN*X, you actually have to run desproxy-dns as root).

       OK, so you have a dns server accessible now. But your computer doesn't know anything about that. You must configure your network
       accordingly (again, need to be root in UN*X).

       Edit /etc/resolv.conf and add the line "nameserver 127.0.0.1". You don't have to restart anything. Just test ping and see if it works.

ENVIRONMENT

       None.

FILES

       None.

SEE ALSO

       dnsproxy(1), ping(1)

AUTHORS

       This manual page was written by Jari Aalto <jari.aalto@cante.net>, for the Debian GNU system (but may be used by others). Released under
       license GPL v2 or any later version.

desproxy-dns							    2012-03-26							   desproxy-dns(1)