Clearing DSN Cache in Raptor 6.5

[Alshrim]

Greetings ..

I recently made some changes to a secondary domain name out on the web for which my firewall is NOT an authority of.

After roughly 48 hours, if I put one of my workstations outside of our firewall.. and forced this machine to use the DSN Name server from our ISP - and did an NSLOOKUP on that domain name .. with a query set to MX - i receive the proper information for that domain name.

However, if i try an NSLOOKUP from within the firewall- the firewall does not return the newly added info.

Is there a way to clear the DSN cache on raptor - so that it is forced to get fresh information? Because I am sure that this problem is the cause of other little sniggling dns issues we've been having.

Any insight would be great. Alshrim
System Administrator
MCSE, MCP+Internet

 

[Alshrim]

Let me specify something... I added an MX record to my domain - which is why i'm doing MX queries. Alshrim
System Administrator
MCSE, MCP+Internet

 

[captnstiles]

If you type at the cmd prompt on the firewall "nslookup" it should return loopback adapter(127.0.0.1). Once nslookup is open, type the name of your ISP's name server, it should return non-authoritative, name.xxx, and IP address of that server. If this does not work, your Daemons DNSD is not configured correctly. You need to make sure you have you Network Interfaces, Network Entities/Hosts, SMTP section setup because you will need this to complete the following. In the DNSD area;
Private:
mailsever MX
localhost.mydomain.com
nameserver.mydomain.com
loopback Interface
NIC card Interface w/internal NIC IP
subnet.in-addr.arpa

Public:
External Recursion (ISP Name Server(1 or 2))
subnet.in-addr.arpa

You need rule 1 to allow mail for the Universe to your server and rule 2 to allow mail out from your server to Universe

You need to make sure that your Name servers use the firewall as their forwarder, if you do not, your cache at your DNS will not populate correctly. As far as I have seen the firewall does not cache, it would be your DNS that does this. I hope this works or helps you with your issue. You did not supply a lot of configuration information to pin point your problem.