Re: Receiving mail for multiple domains (2)

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Steve S (sstogrin_at_remove.sympatico.ca)
Date: 09/21/04 

Date: Tue, 21 Sep 2004 18:26:43 -0400

Receiving from two domains is setup in the exchange recipient policy. the MX
record for the domain needs to point to your server. Unless you are hosting
your own dns entries (which is a whole other animal that you shouldn't be
doing) your server DNS shouldn't matter.

Hope that helps
Steve

"NickC" <me@somewhere.com> wrote in message
news:u0fgqe9nEHA.2948@TK2MSFTNGP11.phx.gbl...
> Still having big problems receiving mail for anything other than the
> default
> domain. The default .net domain works fine now but any mail sent to
> either
> of the secondary domains .com/.org gets the following NDR:
>
> (reason: 550 5.7.1 Unable to relay for Admin@StKittsNevisRegistry.com)
>
> This is a basic install of SBS2003 Standard. The only errors I am seeing,
> apart from the normal Exchange start-up ones, are listed below, and yes I
> have done Mariėtte's time synchronization fix.
>
> Where do I go from here, what can I do next to try and solve this?
>
> Thanks,
> Nick
>
>
> 17 W32Time
> Time Provider NtpClient: An error occurred during DNS lookup of the
> manually
> configured peer 'time.windows.com,0x8'. NtpClient will try the DNS lookup
> again in 15 minutes. The error was: No such service is known. The service
> cannot be found in the specified name space. (0x8007277C)
>
>
> 29 W32Time
> The time provider NtpClient is configured to acquire time from one or more
> time sources, however none of the sources are currently accessible. No
> attempt to contact a source will be made for 15 minutes. NtpClient has no
> source of accurate time.
>
>
> 107 WMIxWDM
> Machine Check Event reported is a fatal error.
>
>
>

Relevant Pages

  • Re: Windows Time Issues
    ... open command prompt ... On server B2 do the following: ... > 1) Time Provider NtpClient: An error occurred during DNS lookup of the ... > DNS lookup again in 30 minutes. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Windows Time Issues
    ... domain is the master time server for the forest. ... > 1) Time Provider NtpClient: An error occurred during DNS lookup of the ... > DNS lookup again in 30 minutes. ...
    (microsoft.public.windows.server.networking)
  • Re: Boot Log
    ... For Time Server issues you can usually resolve that by simply changing ... Time Provider NtpClient: An error occurred during DNS lookup of the ... I don't recall configuring any time programs, ...
    (microsoft.public.windowsxp.general)
  • Re: Time error
    ... I was able to set that for my Server and computers as well as they were ... It seems that I cannot get the time sync up via internet time sync. ... Time Provider NtpClient: An error occurred during DNS lookup of ... NtpClient will try the DNS lookup again in 15 minutes. ...
    (microsoft.public.windows.server.general)
  • Re: Cant Get DC List W32tm /monitor
    ... 'The server process could not be started because the configured identity is ... DCOM got error "Logon failure: unknown user name or bad password. ... Time Provider NtpClient: An error occurred during DNS lookup of the manually ... Installation Successful: ...
    (microsoft.public.windows.server.general)