DNS (Primary & Secondary) Not working

I need a solution

Hi,

I have define Primary DNS as 202.x.x.x.

While in Alternate DNS i have define 8.8.8.8 . We observed that our Primary DNS was down but Secondary DNS was OK. Still all user was getting DNS Unresolved error till Primary DNS back to OK state.

Need to know in which condition alternate DNS will work ? 

0

1539143669

Related:

SPF not working

I do not need a solution (just sharing information)

Hi All,

Rcently I have configured a new SPF on my DNS and in addition SMG support helped me to configure SPF chcker, but from some resaon it doesnt work.

This is the Domain:

Dalas.co.il

SPF details:

> set q=txt
> dalas.co.il
Server:  google-public-dns-a.google.com
Address:  8.8.8.8

Non-authoritative answer:
dalas.co.il     text =

        “v=spf1 ip4:207.232.18.126/32 ip4:5.100.250.205/32 -all”
 

I am trying to send a email through “Contant” on my website: www.dalas.co.il and the mail blocked by SMG because of SPF CHCKER.

The web site IP is 5.100.250.205 which is my website who tries to send email from “dalas@dalas.co.il”

The error on SMG is:

static senderauth fail 
 
0

Related:

The DNS server does not have a cache or other database entry for root name servers. Either the root hints file, cache.dns, or Active Directory must have at least one name server (NS) resource record, indicating a root DNS server and a corresponding host (A) resource record for that root DNS server. Otherwise, the DNS server will be unable to contact the root DNS server on startup and will be unable to answer queries for names outside of its own authoritative zones. To correct this problem, use the DNS console to update the server root hints. For more information, see the online Help.

Details
Product: Windows Operating System
Event ID: 706
Source: DNS
Version: 5.0
Symbolic Name: DNS_EVENT_NO_ROOT_NAME_SERVER
Message: The DNS server does not have a cache or other database entry for root name servers. Either the root hints file, cache.dns, or Active Directory must have at least one name server (NS) resource record, indicating a root DNS server and a corresponding host (A) resource record for that root DNS server. Otherwise, the DNS server will be unable to contact the root DNS server on startup and will be unable to answer queries for names outside of its own authoritative zones. To correct this problem, use the DNS console to update the server root hints. For more information, see the online Help.
   
Explanation

The cache file contains name-to-IP-address mappings for the DNS servers on the Internet root. The cache file is used to resolve over the Internet name queries from outside the enterprise network. DNS automatically installs a cache file in the Systemroot\System32\Dns folder.

   
User Action

Use the cache file that was automatically installed when DNS Manager was installed. If you need to obtain a new copy, connect to internic.net and download the cache file from there. If you cannot connect to the Internet, delete the current cache file and create a new one by first backing up all of your database files and then reinstalling DNS Manager.

Related:

Process %1 (PID=%2). The site monitor API was unable to verify the site name for this Exchange computer – Call=%3 Error code=%4. Make sure that Exchange server is correctly registered on the DNS server.

Details
Product: Exchange
Event ID: 2501
Source: MSExchangeADAccess
Version: 8.0
Symbolic Name: SITEMON_EVENT_CHECK_FAILED
Message: Process %1 (PID=%2). The site monitor API was unable to verify the site name for this Exchange computer – Call=%3 Error code=%4. Make sure that Exchange server is correctly registered on the DNS server.
   
Explanation

This Error event indicates that the Site monitor API did not find the local site name for the server that is running Microsoft® Exchange Server. The Site monitor API discovers the site name where the Exchange server is installed. It also updates the msExchServerSite attribute of the Exchange server object when the local site name changes.

This event may occur for one or more of the following reasons:

  • The Exchange server is not correctly registered on the DNS server.

  • The Site monitor API cannot find the correct domain name.

   
User Action

To resolve this error, do one or more of the following:

  • Make sure that Exchange server is correctly registered on the DNS server. For more information about how to troubleshoot DNS issues, see DNS Troubleshooting.

  • If you have defined multiple sites, make sure that you have created an IP subnet for each site. To configure an IP subnet, do the following:

    1. Start Active Directory® Sites and Services on a local domain controller.

    2. In the left pane, right-click Subnets, and then click New Subnet.

    3. Specify the appropriate configuration information for the new subnet. Make sure that you associate the new subnet with the appropriate site name.

      For more information about how to configure Active Directory sites, see Creating an Active Directory Site for Exchange Server.

  • Review the Application log and System log for any corresponding Warning or Error events.

Note  If you aren’t already doing so, consider running the tools that Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mailflow, and better manage disaster-recovery scenarios. Go to the Toolbox node of Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related: