DNS HELP!

I am still hanging in there and making progress, very slowly. I am new to all things servers and am trying to get this up and running. While setting up DNS, I have a few questions:
How do I know if I am using a workgroup, standard, or advanced server. I'm using lynda.com to configure DNS.
This server was already installed but doesn't work and it was given to me to make work.
My end goal is to be able to ftp to server and then us feeder for itunesU. Right now the feeder url are unrecognizable so I decided to start back with DNS. Is there a chat room where I can get help with this? My company is a startup and don't have money to send me to a class.

http://discussions.apple.com/index.jspa?categoryID=1 -->Server Products has these:
Mac OS X Server
Xserve
Xserve RAID
Xsan
Apple Remote Desktop
Final Cut Server
Pick the appropriate poison.

Similar Messages

  • DNS Help: Configure for local and extenal services using same domain name?

    Hello all. I'm setting up a 10.5 server, have scoured these great forums and gotten close, but am still stuck. Any help would be greatly appreciated.
    My network setup is as follows: Internet (2xT1) > modem > router/firewall/NAT device > XServe > switches > rest of network, clients, etc. Pretty standard, I believe.
    I'd like to use this XServe on our local network/intranet/LAN only for OD, networked home directories, AFP, iCal, Time Machine, Print and Software Update.
    My website is hosted on an external server.
    My email is also hosted on a (different) external server.
    Domain is school.edu
    XServe name is xserve.school.edu
    XServe is 10.0.0.25
    I've gone through Apple's recommended DNS setup (supplemented by some great info found here on the forums....), and am able to connect to other Internet sites (with client's DNS server set as 10.0.0.25), but unable to connect to www.school.edu, or send/receive mail to/from mail.school.edu.
    In short, connecting to external domains that are NOT related to my school are fine, but I'm unable to connect to any domain that IS related to my school.
    If anyone out there can shoot me some notes on how to configure the DNS settings, zones, forwarding, etc. to accomplish this, I'd be VERY appreciative.
    Thanks, in advance, to anyone who can help me out.
    Cheers,
    Tim

    In short, connecting to external domains that are NOT related to my school are fine, but I'm unable to connect to any domain that IS related to my school.
    If your server thinks it's authoritative for 'school.edu' then you have to add records for every host in the school.edu zone.
    For example, if you want to be able to resolve 'www.school.edu' then you have to have a 'www' record. If you want to send/receive mail you have to add an MX record, and so on.
    It doesn't matter that you're not responsible for those servers, it's just that since this machine thinks it 'owns' school.edu it will only respond with records in its own zone and won't care about what any other name server says, even if that other name server is authoritative for the zone.
    FWIW, that's often why people running stub servers like this choose a separate subdomain (like 'dept.school.edu') so they can leave the main school.edu records on the main server and have full control over a subdomain.

  • Basic Mail and DNS help

    I'm sorry to ask something that I'm sure has been dealt with many times. I've searched all around and found many threads that seem very close, but I guess there's some little difference that always ends up confusing me. I also get confused by what seems to me to be ambiguous terminology. Anyway, I'm pulling my hair out, so I've finally decided to ask for help.
    I'm sorry that this post is so long -- I just don't know what bit of info might be important. I'm trying to give a detailed description of my setup so experienced people can give me better advice.
    Here's my situation.
    EXTERNAL DNS
    (1) I've purchased a domain name through my ISP. Let's call it mydomain.tld
    (2) This comes with a very rudimentary control panel that allows me to define 10 A records, 10 CNAME records and 10 MX records.
    (3) I have defined an A record pointing to my static WAN IP.
    (4) I have deifined an MX record pointing to the same static WAN IP.
    (5) This seems to be OK, because if I "dig mydomain.com" or "dig MX mydomain.com" I get my static WAN IP.
    MY LITTLE NETWORK
    (6) The Internet comes into a 4-port router/modem. (192.168.0.x) This is my "Outer LAN"
    (7) One port goes to a Mini with SLS -- Say it's on 192.168.0.99
    (8) Another port goes to another router (192.168.1.x) This is my "Inner LAN"
    (9) I have forwarded port 80 through the outer router to the SLS. That seems to work fine.
    (10) I have also forwarded port 25 through the outer router to the SLS. That does not work yet.
    The SLS
    (11) When I did the initial install, I gave the SLS the name mydomain.private (I some places, Server Admin gives the name mydomain.local ... I don't know why.)
    (12) I set up the INTERNAL DNS on the SLS to handle all initial DNS queries from my LANs, with my ISP's DNS as a forwarder.
    (13) I set up the DHCP on my routers to assign the internal DNS server on the SLS as the primary DNS, and my ISP's DNS server as the secondary -- so clients on my LANS are looking at the right DNS servers.
    (14) DNS seems to work fine on both my LANs.
    BEFORE GOING ANY FURTHER:
    If anyone sees any problems with what I have done so far -- Please say so.
    ... and now THE MAIL
    (15) I created a few network user accounts on SLS.
    (16) Using squirrelmail, they were able to send and receive messages to each other -- using a browser on the SLS machine or a browser on any other computer on the LANs. But this is all resolved through the internal DNS, using mydomain.private
    (17) Mail clients (Mail.app) on the LAN can also retrieve these messages. But I can't send mail using a regular mail client ... and squirrelmail only works internally with mydomain.private
    Now, I want to get my mail server working normally for sending and receiving mail both within my LAN and over the Internet. And here is where I get confused. There's the EXTERNAL DNS server that clients on the Internet will use to find my server -- and there's the INTERNAL DNS server that clients on my LAN (?and possibly some services on the server itself?) will use. Then there are terms like HOSTNAME and DOMAIN NAME ... and I'm not really very clear as to the disnction (despite, or because of, reading so many articles). I don't know where I should be using mydomain.com and where I should be using mydomain.private)
    in the Mail Service Configuration Assistant:
    (18) I use mydomain.com for both the Domain Name (Enter the local Internet domain name) and for the Host name (enter the Internet host name of this mail system). These match the A and MX records of my EXTERNAL DNS (ie. what I see on my ISP's control panel).
    (19) To try to make things easier to start with, I enabled all options for both secure and non-secure authentication.
    (20) I added a host alias mydomain.private
    (21) Setup appeared to go fine.
    (22) Back on the LAN, "dig MX mydomain.com" gives my static WAN IP
    (23) In the outer router, port 25 is forwarded to the SLS
    (24) In SLS, in Server Assistant, In DNS, Mail Exchanger is set to mydomain.private -- this works for sending mail within the LAN only.
    (25) I tried changing this to mydomain.com, and then nothing worked.
    (26) The Nameserver for my primary zone is set to:
    Zone: mydomain.private.
    Hostname: mydomain.private
    When I try to send a message FROM an account on the Internet TO an account on the SLS, I get an error: "Couldn't find a Mail Exchanger or IP address."
    When I try to send a message FROM an account on the SLS TO an account on the Internet, the Mail Delivery System returns it to the sender.
    Well, that's where I stand now.
    I hope people reading will give me some ideas of some other paths to run down, and tests or experiments to try. I'm not afraid of the command line -- but I'm not very experienced with it either -- so maybe there are some useful diagnostic commands that I should know about.
    My ISP is not blocking port 80.
    Is there some way that I can tell if my ISP is blocking port 25? (Their customer support doesn't know anything.)
    Thanks a lot for your attention and patience.
    (Intentionally Blank)

    Oops. Sorry for the delay getting back to you.
    Thanks David_x. That was really helpful information. It opened up more questions, but it gave me some good ideas of things to try.
    I reinstalled SLS. This time I used my FQDN and accepted the installer's
    David_x wrote:
    Firstly, remove the secondary from DHCP. Otherwise clients will 'randomly' use info from either inside or outside DNS. You want them to use the internal DNS so use that alone.
    I see. So "secondary" doesn't mean "in case the primary fails" -- it means something more like "another one in the pool of possible DNS servers". Doesn't that present a problem in the event that my server is down? Why is this preferred as opposed to clearly defined prioritized list? (Then there is another issue of some services using mDNSResponder in some cases and resolv.conf -- at least that's fairly well documented.)
    DNS & Hostname, etc...
    If you want to be able to access services from inside and outside your LAN, using the server's hostname (same one inside and out), then set up your internal DNS using your .com domain, same as is used externally.
    Okay. Got it. I did that with the reinstall.
    DNS is only an "IP lookup" system so you want the hostname inside to resolve to your LAN IP and the hostname outside to resolve to your WAN IP. Forget about the .private stuff - it just confuses things.
    Okay. Thanks.
    Public MX Record…
    (3) I have defined an A record pointing to my static WAN IP.
    (4) I have deifined an MX record pointing to the same static WAN IP.
    The above may not be what you meant to say but just to check… Your public MX record should resolve to your A record hostname. Then the hostname resolves to an IP address. Your MX record should not be pointing directly to an IP address.
    Yes. You are right. That's very good of you to point that out. I did have it pointing to an IP address. (My ISPs simplistic DNS control panel is in Spanish, and I was confused about whether "nombre" referred to a name or number.) I had discovered this through brute force trial and error. This sort of thing was very difficult to test, since I don't have control over many of the DNS parameters (like TTL). That was probably my main problem. Now I can send and receive mail from my server to outside accounts, and from outside accounts to my server.
    At the moment, I can't retrieve mail on my server from a computer outside of my network. I suppose that's an authentication problem, or a hostname alias or something. I'll continue trying different things.
    Testing Port 25...
    To see if port 25 is blocked, get an outside computer and "telnet your-wan-ip 25". If you can switch on logging at the firewall for your port-forwarding rule, all the better as this will be only sure way to see that it is reaching the WAN firewall.
    By "logging at the firewall", I suppose you mean at the router? Alright. I still have to try this. From my point of view, this kind of suggestion is great advice.
    Instead of using an outside computer, would it be possible to do this sort of checking using an anonymizing proxy? I suppose they usually don't allow telnet.
    ...any chance this could be tested from my "inner" LAN? (My guess is that it needs to be from a computer that is "upstream" relative to the "outer" router. I'm under the impression that routers handle upstream connections differently than downstream connections, this wouldn't work.)
    After that, test at server... open Terminal and enter: "tcpdump -v tcp port 25"
    Tcpdump will listen on port 25. When the telnet session gets port-forwarded, you will see a listing of information about the packet received. If you get nothing then the port-forwarding is not working.
    So, to make sure I've got this straight:
    Turn on logging on port 25 in my outer router.
    Go to Terminal on my server.
    Start tcpdump listening on port 25.
    Take my netbook out to some WiFi hotspot (for example).
    Telnet into my server.
    Come home and check my logs.
    (Maybe I should check out this VPN stuff.)
    I'm looking to see that the router forwarded the port correctly.
    That's great trouble shooting advice.
    Now you'll see how slow I am. I'm reading along, running through all of this in my head, imagining all of my steps ... And only now do I realize that if (as of my latest experiments) my server has been able to receive mail from outer accounts -- then the router must be forwarding things and the mail server is, to some extent, working fine. Okay. I'm still going to go through these steps anyway to see what it should look like.
    Server Admin: Domain Name & Hostname...
    The Domain Name is just your domain name... e.g., mydomain.com
    The Hostname is ideally the same as your external MX hostname... e.g., mail.mydomain.com
    The main thing about the Hostname is that this is what your server will report as it's HELO name to other connecting mail servers. Some will check this against the public MX record and use any discrepancy to increase likelihood of spam filtering.
    Is there really any reason that a small setup like mine should use "mail.mydomain.com" instead of just "mydomain.com". Since I don't have a separate machine dedicated to mail, maybe it's just an unnecessary complication. I was just copying what I've seen around (configuration for mail and articles I've read).
    Under Advanced-> Hosting, tick the "Include server's domain as local host alias".
    Okay. What exactly does this do? I understand the words, but not the sense of the phrase. (I find this happening a lot.)
    Checking Server Settings…
    Use a terminal session to debug any basic configuration issues on the server. The error responses are much more informative than just using a mail client. Open Terminal in a local computer… "telnet server-lan-ip 25" and carry out following…
    I could connect with telnet to port 25 on the server:
    (1) From a remote computer.
    (2) From a local client.
    (3) From the server
    As we step through the experiment, you will see that we have a few problems.
    Server Response:
    Trying...
    Connected to fqdn.or.ip.
    Escape character is '^]'.
    220 fqdn.or.ip ESMTP Postfix
    #1. Declare where you are sending the email from:
    HELO something.name
    You can use a real hostname but the mail server has no choice but to accept whatever you type.
    Response: 250 servers.hostname
    So far, so good.
    On remote computers, I couldn't get any further than this.
    I'll try again tonight.
    #2. Give senders address:
    MAIL FROM:<mail@senderdomain>
    Response: 250 Ok
    I could get this to work for either a local email account or a remote email account, from telnet sessions initiated either on the server itself or on a local client.
    #3. Give recipients address:
    RCPT TO:<mail@otherdomain>
    Response: 250 Ok
    Here, I did not get consistent results.
    From a local account to a remote account, I could get "Relay access denied".
    From a local account to a local account, I could get "Recipient address rejected. Service is unavailable. But this was not consistent. I used three different local accounts, and all could send or receive at one time or another.
    #4. Start composing the message:
    DATA
    Response: 354 End data with <CR><LF>.<CR><LF>
    #5. Type a message. Finish with a single "." on a line on it's own.
    Response: 250 Ok: queued as dah,de,da
    #6. Close the connection by typing: QUIT
    Response:221 Bye... Connection closed by foreign host.
    suggestion for hostname.
    Were you going to add something else here?
    Well, any comments or insights that you might add will be very much appreciated. I'm going to continue sending and receiving and making little tweaks. It's really pretty confusing for a newbie. I thank you a lot for all the time you spent reading and helping me.
    (Intentionally Blank)

  • Open DNS & Airport Question

    I have a wireless network (Airport Extreme and Airport Express for range in the back of my house). Have 4 Macs on the network. All have Open DNS set in System Prefs>Network>Airport>Advanced>DNS.
    Should I set one or both of the Airports to Open DNS also? If so, how? I looked at Airport Utility and see no ready way to do it.
    If I should add OPen DNS to Airport, can someone tell me how in an easy to follow fashion?
    Thanks in advance!

    No, sorry.
    All my machines are individually set for Open DNS: System Prefs>Network>Airport>Advanced>DNS: 208.67.222.222; 208.67.220.220.
    The machines have been set this way for a long time.
    My Q: Can/Should I set my Airports (Express and Extreme) somehow for Open DNS?
    My general configuration is:Cable>Modem>Airport>4 Macs.
    The hardware configuration is Cable into Router (Cox), Ethernet into Extreme, broadcast to Express 5 rooms away (to serve 2 of the 4 Macs); Ch 1 all.
    Perfect connection - so don't want to mess with that.
    Just want to know (if I can to speed up download time) --
    Would (if possible) setting the Airport settings to Open DNS help my speed? If so, how in the world would one do that - - > set the actual base station to have Open DNS settings?
    Make sense? Hope so!
    Thanks!
    Message was edited by: pcbjr

  • DNS Setting for internal sites

    Hello -
    I've had terrible problems with my internet connection recently. No internet connection = no DNS (using Google) and therefore I can't even access sites which are hosted within my own network.
    Could anyone talk me through adding DNS references to internal sites on SLS ?
    My set up :
    ADSL modem (bridge mode) into Airport Express which runs DHCP / NAT
    SLS connected to Airport which has DNS server already running.
    changeip -checkhostname returns
    Primary address = 10.0.1.2
    Current HostName = xx.xxx.ltd.uk
    DNS HostName = xx.xxx.ltd.uk (changed these entries)
    The names match. There is nothing to change.
    dirserv:success = "success"
    My domain name is registered with an external supplier - and set to point to my static IP address.
    Thanks for any help !
    Andrew

    One thing that did help me though - and this may be obvious to you, but I had problems with Server admin crashing. Changing the DNS server in network preferences on the server itself and the client I was working on to a public DNS helped. Guess that should be pretty obvious though.
    If things get wonky, I usually try to run Server Admin directly on the target server box.
    Am I safe to reference the DNS server on the client now as dns.mydomain.com ? ie - if that is where the client is getting it's DNS references from, how does it know where dns.mydomain.com points to before it looks it up ?!
    DNS servers are referenced by IP address, not by host name. Until the DNS server is available, the DNS names won't work; a bootstrapping problem.
    As for testing the server, you can use the dig command to test.
    +dig @ip.addr.dns.server whatever+
    Also - I am using an Airport Base Station for DHCP / NAT - but can't see how I can specify a DNS server so that all clients receive it automatically ? (This is fine for clients that don't leave the office, but a pain for laptops)
    AirPort Utility > select target AirPort > Manual setup > Internet > DNS Servers

  • Host my own DNS

    Please help me!!!
    I have a G5 XServe, running OS X Server 10.4.8. I am trying to host my own DNS on my XServe, meaning I logged into my account at GoDaddy.com and changed my DNS servers to ns1.mydomain.com and ns2.mydomain.com.
    I used to have the server behind a router, and just had ports and traffic forwarded to it. Now, I have put it in front of the router and assigned it one of the static IPs (as per my ISP), and can connect to the internet. I didn't have any problems resolving addresses before I moved the DNS at GoDaddy. I can ping the server via ns1.mydomain.com, but that's it. I can't ping mydomain.com or mail.mydomain.com, both of which have been set up in Server Admin.
    Here is the weird thing: I wiped out all of my DNS Zone entries in Server Admin, but I can still view a different site I host. When I ping it, it resolves to the local IP I have specified, ie 192.168.1.10.
    I've been using Server Admin to set up the DNS service. I've read contrasting opinions on this. Some stating that DNS should be administered through the command line, some that Server Admin is fine. Thoughts? I prefer to use the Server Admin, as I'm not terribly comfortable using the command line (ex-Windows guy. Sorry).
    Any insight, help, voodoo hexes are greatly appreciated. Thanks.

    Ok , first welcome to mac os x server ,
    About DNS setup.
    Since you want to setup your own service you have to keep a few things in mind.
    a) your server machine HAS to have a Fixed IP address : for that you have to configure one of you WAN addresses to that machine : for example if you are provided an adress like 80.200.110.16 with a subnet of 255.255.255.248 your network will start at 80.200.110.16 to 80.200.110.23 since you have 5 ips i would say one address is reserved to your router and shall be kept that way one is your broadcast (probably the end address) the other adresses in between are all yours.
    b) if you can turn off the router's DCHP server do so , your DNS machine is supposed to be your 24/7 at some point and since you might want to run everything at gigabit speed it does not make sense to have your traffic routed to your router at all times.
    2) DNS registration and domain registration; pick your domain from a nice registrar : i would suggest network solutions and declare the following.If you are changing ISP and already have a domain name make SURE you have control of your domain name and/or ask the transfer operated your favorite registrar. If you have full control of your domain's registration your domain change is down to a change of IP adresses in the registrars records.
    a) If you want a new domain name attributed to your machine 80.200.110.17 (your server) during the whole article ill suppose your 80.200.110.16 is your router. Setup your records ,hostnames etc.
    b) Keep in mind any new registration for a domain to get validated takes TIME (about 72 hours) for it to reach root servers , the system just updates itself on a regular basis.
    b1) after you have registred and or upated your Domain with your registrar you have to setup your DNS records here follows a quick example of a forward DNS (home server)
    db.domain that is the forward zone , this is stored in /var/named
    maxosx.net. IN SOA moxxy.domain.net. [email protected]. (
    1 ; Serial
    10800 ; Refresh after 3 hours
    3600 ; Retry after 1 hour
    604800 ; Expire after 1 week
    86400 ) ; Minimum TTL of 1 day
    ; Name servers
    maxosx.net. IN NS moxxy.maxosx.net.
    ; Addresses for the canonical names
    localhost.domain.net. IN A 127.0.0.1
    moxxy. domain.net. IN A 80.200.110.17
    www. domain.net. IN A 80.200.110.17
    ftp. domain.net. IN A 80.200.110.17
    sftp. domain.net. IN A 80.200.110.17
    domain.net. IN A 80.200.110.17
    moxxy. domain.net. IN A 80.200.110.17
    mail. domain.net. IN A 80.200.110.17
    pop3. domain.net. IN A 80.200.110.17
    smtp. domain.net. IN A 80.200.110.17
    imap. domain.net. IN A 80.200.110.17
    pop. domain.net. IN A 80.200.110.17
    leopard.domain.net. IN A 80.200.110.17
    gateway.domain.net. IN A 80.200.110.16
    ;DHCP Range
    ; MX Records
    domain.net. IN MX 0 mx.domain.net.
    Second file the reverse record:
    ; File created by DNS Helper vendredi 8 décembre 2006 11:30:53
    142.80.81.in-addr.arpa. IN SOA moxxy.maxosx.net. [email protected]. (
    1 ; Serial
    10800 ; Refresh after 3 hours
    3600 ; Retry after 1 hour
    604800 ; Expire after 1 week
    86400 ) ; Minimum TTL of 1 day
    ; Name Servers
    110.200.80.in-addr.arpa. IN NS moxxy.domain.net.
    ; Addresses point to canonical name
    17.110.200.80.in-addr.arpa. IN PTR moxxy.domain.net.
    17.110.200.80.in-addr.arpa. IN PTR www.domain.net.
    17.110.200.80.in-addr.arpa. IN PTR ftp.domain.net.
    17.110.200.80.in-addr.arpa. IN PTR sftp.domain.net.
    17.110.200.80.in-addr.arpa. IN PTR domain.net.
    17.110.200.80.in-addr.arpa. IN PTR moxxy.domain.net.
    17.110.200.80.in-addr.arpa. IN PTR mail.domain.net.
    17.110.200.80.in-addr.arpa. IN PTR pop3.domain.net.
    17.110.200.80.in-addr.arpa. IN PTR smtp.domain.net.
    17.110.200.80.in-addr.arpa. IN PTR imap.domain.net.
    17.110.200.80.in-addr.arpa. IN PTR pop.domain.net.
    17.110.200.80.in-addr.arpa. IN PTR leopard.domain.net.
    c) If you are unfamilliar with DNS Setup and pico editing a DNS record i cannot recommend apple's DNS GUI and would recommend menandmice DNS server over apple's not that Apple's DNS server is broken far from it , the GUI is not made to handle anything but a local DNS service.
    c1) there is also a free tool named DNS Helper that works great with apple's DNS server , BUT it is at a loss to calculate serials for DNS records ,
    http://mail.computertree.com/~josh/simple/dnshelper.html
    c2) MenandMice DNS server.
    http://www.menandmice.com/
    d) Make sure your mac os X's firewall is properly setup your ipfw shall authorize traffic from port 53 on UPD and TCP both in inbound and outbound queries.
    e) once you setup your DNS Make SURE your dns servers wan address figures in your TCP/IP DNS records setup on your main port , otherwise your server might not just operate
    f) if you wish as well to edit your hostname in the hostconfig it will not hurt as well ... it is located in /etc/hostconfig and or you can choose changeip as noted abobe my post by Greg Pearman.
    g) for DHCP purposes you can surely use the Apple's Gateway assistant which works 100 percent fine on mac os X server 10.4.8.
    Hoping this helps you in your setup.
    Ps: Thanks to david for posting the Dns Diagnostic tools link as well this is dead handy
    http://www.dnsreport.com/tools/dnsreport.ch?domain=dysl.net
    MacPro 2.66Ghz 8GB Ram 4*500GB waiting for X1900XT   Mac OS X (10.4.8)   Mac os X server 10.4.8 Universal Binary

  • HT201250 light is amber, no dns on my time machine

    my issue with time machine is it says another network is using my id. Now amber light is continous evenafter restartins, and says I hve no dns help please

    DNS stand for Domain Name Server, it's a server your ISP (usually unless it's changed) uses to resolve a Domain Name like Apple.com into a iP address like 94.174.85.343 (only a example) this way your computer can connect to that IP address.
    Because the IP address can change and keep it's smae name, like a business can change location yet still remain the same name, the DNS is updated to reflect these changes so your connecting to the correct site.
    Your signature says your on 10.6.3, this is outdated, I hope you have at least updated to 10.6.8 under the Apple menu > Software Update. Applying security updates is important.
    When you say another computer is using your id, that means something is wrong that another comptuer on your local network is using the same local IP that your machine is using.
    You seem to have a lot of issues and perhaps don't know a whole lot about computers and networks, it wouldn't be a bad decision to call in a local professional to resolve your problems and secure your network, look for trjoans (Flashback) you may installed on your machine by accident.
    I suspect this is what has happened, as the DNS is changed. It might be your ISP DNS server is down, you might want to wait.
    Why your TimeMachine drive is not funtional is another strange issue. Perhaps you have it confused with something else?
    More information is required and we may be able to assist.

  • Verifying DNS Record Readiness fails before domain rename

    I'm in the process of a domain rename. I am verifying DNS readiness (see: http://technet.microsoft.com/en-us/library/cc816721(v=ws.10).aspx)When I run the command: Dcdiag /test:DNS /DnsRecordRegistration /s:<my domaincontroller>I get the following errors:Directory Server Diagnosis
    Performing initial setup:
       * Identified AD Forest.
       Done gathering initial info.
    Doing initial required tests
       Testing server: AZ01\DC1PHX
          Starting test: Connectivity
             ......................... DC1PHX passed test Connectivity
    Doing primary tests
       Testing server: AZ01\DC1PHX
          Starting test: DNS
             DNS Tests are running and not hung. Please wait a few minutes...
             ......................... DC1PHX passed test DNS
       Running partition tests on : ForestDnsZones
       Running partition tests on : DomainDnsZones
       Running partition tests on : Schema
       Running partition tests on : Configuration
       Running partition tests on : corp
       Running enterprise tests on : corp.l**t.net
          Starting test: DNS
             Test results for domain controllers:
                DC: dc1phx.corp.l**t.net
                Domain: corp.l**t.net
                   TEST: Records registration (RReg)
                      Network Adapter [00000016] Hyper-V Virtual Ethernet Adapter:
                         Warning:
                         Missing CNAME record at DNS server 172.17.0.3:
                         <GUID>._msdcs.corp.l**t
    net
                         Warning:
                         Missing A record at DNS server 172.17.0.3:
                         dc1phx.corp.l**t.net
                         Error:
                         Missing SRV record at DNS server 172.17.0.3:
                         _ldap._tcp.corp.l**t.net
                         Error:
                         Missing SRV record at DNS server 172.17.0.3:
                         _ldap._tcp.<guid>.domains._mdcs.corp.l**t.net
                         Error:
                         Missing SRV record at DNS server 172.17.0.3:
                         _kerberos._tcp.dc._msdcs.corp.l**t.net
                         Error:
                         Missing SRV record at DNS server 172.17.0.3:
                         _ldap._tcp.dc._msdcs.corp.l**t.net
                         Error:
                         Missing SRV record at DNS server 172.17.0.3:
                         _kerberos._tcp.corp.l**t.net
                         Error:
                         Missing SRV record at DNS server 172.17.0.3:
                         _kerberos._udp.corp.l**t.net
                         Error:
                         Missing SRV record at DNS server 172.17.0.3:
                         _kpasswd._tcp.corp.l**t.net
                         Error:
                         Missing SRV record at DNS server 172.17.0.3:
                         _ldap._tcp.AZ01._sites.corp.l**t.net
                         Error:
                         Missing SRV record at DNS server 172.17.0.3:
                         _kerberos._tcp.AZ01._sites.dc._msdcs.corp.l**t.net
                         Error:
                         Missing SRV record at DNS server 172.17.0.3:
                         _ldap._tcp.AZ01._sites.dc._msdcs.corp.l**t.net
                         Error:
                         Missing SRV record at DNS server 172.17.0.3:
                         _kerberos._tcp.AZ01._sites.corp.l**t.net
                         Error:
                         Missing SRV record at DNS server 172.17.0.3:
                         _ldap._tcp.gc._msdcs.corp.l**t.net
                         Warning:
                         Missing A record at DNS server 172.17.0.3:
                         gc._msdcs.corp.l**t.net
                         Error:
                         Missing SRV record at DNS server 172.17.0.3:
                         _gc._tcp.AZ01._sites.corp.l**t.net
                         Error:
                         Missing SRV record at DNS server 172.17.0.3:
                         _ldap._tcp.AZ01._sites.gc._msdcs.corp.l**t.net
                   Error: Record registrations cannot be found for all the network
                   adapters
             Summary of DNS test results:
                                                Auth Basc Forw Del  Dyn  RReg Ext
                Domain: corp.l**t.net
                   dc1phx                       PASS PASS n/a  n/a  n/a  FAIL n/a
             ......................... corp.l**t.net failed test DNS
    Help please :)

    Thanks :)
    I just ran dnslint between the two root DCs. It's strange, they don't list any missing glue records.
    DNSLint Report
    System Date: Sun Jun 29 09:11:29 2014 
    Command run: 
    dnslint /ad 172.17.0.3 /s 172.16.0.4
     Root of Active Directory Forest: 
        corp.l**t.net
    Active Directory Forest Replication GUIDs Found:
    DC: DC1NY
    GUID: <My GUID>
    DC: DC1NYLV
    GUID: <My GUID>
    DC: DC1NYLVPS
    GUID: <My GUID>
    DC: DC1PHX
    GUID: <My GUID>
    DC: DC1PHXLV
    GUID: <My GUID>
    DC: DC1PHXLVPS
    GUID: <My GUID>
    Total GUIDs found: 6
    The following 6 DNS servers were checked for records related to AD forest replication:
    DNS server: dc1ny.corp.l**t.net
    IP Address: 172.16.0.4
     UDP port 53 responding to queries: YES
    TCP port 53 responding to queries: Not tested
    Answering authoritatively for domain: YES
    SOA record data from server:
     Authoritative name server: dc1ny.corp.l**t.net
    Hostmaster: hostmaster.corp.l**t.net
    Zone serial number: 134
    Zone expires in: 1.00 day(s)
    Refresh period: 900 seconds
    Retry delay: 600 seconds
    Default (minimum) TTL: 3600 seconds
    Additional authoritative (NS) records from server:
     dc1phxlv.l**t.com Unknown
     dc1nylvps.l**tp**g.com Unknown
     dc1ny.corp.l**t.net Unknown
     dc1nylv.l**t.com Unknown
     dc1phxlvps.l**tp**g.com Unknown
     dc1phx.corp.l**t.net Unknown
    Alias (CNAME) and glue (A) records for forest GUIDs from server:
     CNAME: <My GUID>._msdcs.corp.l**t.net
    Alias: dc1ny.corp.l**t.net
    Glue: 172.16.0.4
    CNAME: <My GUID>._msdcs.corp.l**t.net
    Alias: dc1nylv.l**t.com
    Glue: 172.16.0.20
    CNAME: <My GUID>._msdcs.corp.l**t.net
    Alias: dc1nylvps.l**tp**g.com
    Glue: 172.16.0.21
    CNAME: <My GUID>._msdcs.corp.l**t.net
    Alias: dc1phx.corp.l**t.net
    Glue: 172.17.0.3
    CNAME: <My GUID>._msdcs.corp.l**t.net
    Alias: dc1phxlv.l**t.com
    Glue: 172.17.0.12
    CNAME: <My GUID>._msdcs.corp.l**t.net
    Alias: dc1phxlvps.l**tp**g.com
    Glue: 172.17.0.13
    Total number of CNAME records found on this server: 6
    Total number of CNAME records missing on this server: 0
    Total number of glue (A) records this server could not find: 0
    DNS server: dc1phxlv.l**t.com
    IP Address: 172.17.0.12
     UDP port 53 responding to queries: YES
    TCP port 53 responding to queries: Not tested
    Answering authoritatively for domain: YES
    SOA record data from server:
     Authoritative name server: dc1phxlv.l**t.com
    Hostmaster: hostmaster.corp.l**t.net
    Zone serial number: 134
    Zone expires in: 1.00 day(s)
    Refresh period: 900 seconds
    Retry delay: 600 seconds
    Default (minimum) TTL: 3600 seconds
    Additional authoritative (NS) records from server:
     dc1ny.corp.l**t.net Unknown
     dc1nylv.l**t.com Unknown
     dc1phxlvps.l**tp**g.com Unknown
     dc1phx.corp.l**t.net Unknown
     dc1phxlv.l**t.com Unknown
     dc1nylvps.l**tp**g.com Unknown
    Alias (CNAME) and glue (A) records for forest GUIDs from server:
     CNAME: <My GUID>._msdcs.corp.l**t.net
    Alias: dc1ny.corp.l**t.net
    Glue: 172.16.0.4
    CNAME: <My GUID>.corp.l**t.net
    Alias: dc1nylv.l**t.com
    Glue: 172.16.0.20
    CNAME: <My GUID>._msdcs.corp.l**t.net
    Alias: dc1nylvps.l**tp**g.com
    Glue: 172.16.0.21
    CNAME: <My GUID>._msdcs.corp.l**t.net
    Alias: dc1phx.corp.l**t.net
    Glue: 172.17.0.3
    CNAME: <My GUID>._msdcs.corp.l**t.net
    Alias: dc1phxlv.l**t.com
    Glue: 172.17.0.12
    CNAME: <My GUID>._msdcs.corp.l**t.net
    Alias: dc1phxlvps.l**tp**g.com
    Glue: 172.17.0.13
    Total number of CNAME records found on this server: 6
    Total number of CNAME records missing on this server: 0
    Total number of glue (A) records this server could not find: 0
    DNS server: dc1nylvps.l**tp**g.com
    IP Address: 172.16.0.21
     UDP port 53 responding to queries: YES
    TCP port 53 responding to queries: Not tested
    Answering authoritatively for domain: YES
    SOA record data from server:
     Authoritative name server: dc1nylvps.l**tp**g.com
    Hostmaster: hostmaster.corp.l**t.net
    Zone serial number: 134
    Zone expires in: 1.00 day(s)
    Refresh period: 900 seconds
    Retry delay: 600 seconds
    Default (minimum) TTL: 3600 seconds
    Additional authoritative (NS) records from server:
     dc1ny.corp.l**t.net Unknown
     dc1nylv.l**t.com Unknown
     dc1phxlvps.l**tp**g.com Unknown
     dc1phx.corp.l**t.net Unknown
     dc1phxlv.l**t.com Unknown
     dc1nylvps.l**tp**g.com Unknown
    Alias (CNAME) and glue (A) records for forest GUIDs from server:
     CNAME: <My GUID>._msdcs.corp.l**t.net
    Alias: dc1ny.corp.l**t.net
    Glue: 172.16.0.4
    CNAME: <My GUID>._msdcs.corp.l**t.net
    Alias: dc1nylv.l**t.com
    Glue: 172.16.0.20
    CNAME: <My GUID>._msdcs.corp.l**t.net
    Alias: dc1nylvps.l**tp**g.com
    Glue: 172.16.0.21
    CNAME: <My GUID>._msdcs.corp.l**t.net
    Alias: dc1phx.corp.l**t.net
    Glue: 172.17.0.3
    CNAME: <My GUID>._msdcs.corp.l**t.net
    Alias: dc1phxlv.l**t.com
    Glue: 172.17.0.12
    CNAME: f<My GUID>._msdcs.corp.l**t.net
    Alias: dc1phxlvps.l**tp**g.com
    Glue: 172.17.0.13
    Total number of CNAME records found on this server: 6
    Total number of CNAME records missing on this server: 0
    Total number of glue (A) records this server could not find: 0
    DNS server: dc1nylv.l**t.com
    IP Address: 172.16.0.20
     UDP port 53 responding to queries: YES
    TCP port 53 responding to queries: Not tested
    Answering authoritatively for domain: YES
    SOA record data from server:
     Authoritative name server: dc1nylv.l**t.com
    Hostmaster: hostmaster.corp.l**t.net
    Zone serial number: 134
    Zone expires in: 1.00 day(s)
    Refresh period: 900 seconds
    Retry delay: 600 seconds
    Default (minimum) TTL: 3600 seconds
    Additional authoritative (NS) records from server:
     dc1nylvps.l**tp**g.com Unknown
     dc1ny.corp.l**t.net Unknown
     dc1nylv.l**t.com Unknown
     dc1phxlvps.l**tp**g.com Unknown
     dc1phx.corp.l**t.net Unknown
     dc1phxlv.l**t.com Unknown
    Alias (CNAME) and glue (A) records for forest GUIDs from server:
     CNAME: <My GUID>._msdcs.corp.l**t.net
    Alias: dc1ny.corp.l**t.net
    Glue: 172.16.0.4
    CNAME: <My GUID>._msdcs.corp.l**t.net
    Alias: dc1nylv.l**t.com
    Glue: 172.16.0.20
    CNAME: <My GUID>._msdcs.corp.l**t.net
    Alias: dc1nylvps.l**tp**g.com
    Glue: 172.16.0.21
    CNAME: <My GUID>._msdcs.corp.l**t.net
    Alias: dc1phx.corp.l**t.net
    Glue: 172.17.0.3
    CNAME: <My GUID>._msdcs.corp.l**t.net
    Alias: dc1phxlv.l**t.com
    Glue: 172.17.0.12
    CNAME: f<My GUID>._msdcs.corp.l**t.net
    Alias: dc1phxlvps.l**tp**g.com
    Glue: 172.17.0.13
    Total number of CNAME records found on this server: 6
    Total number of CNAME records missing on this server: 0
    Total number of glue (A) records this server could not find: 0
    DNS server: dc1phxlvps.l**tp**g.com
    IP Address: 172.17.0.13
     UDP port 53 responding to queries: YES
    TCP port 53 responding to queries: Not tested
    Answering authoritatively for domain: YES
    SOA record data from server:
     Authoritative name server: dc1phxlvps.l**tp**g.com
    Hostmaster: hostmaster.corp.l**t.net
    Zone serial number: 134
    Zone expires in: 1.00 day(s)
    Refresh period: 900 seconds
    Retry delay: 600 seconds
    Default (minimum) TTL: 3600 seconds
    Additional authoritative (NS) records from server:
     dc1phxlvps.l**tp**g.com Unknown
     dc1phx.corp.l**t.net Unknown
     dc1phxlv.l**t.com Unknown
     dc1nylvps.l**tp**g.com Unknown
     dc1ny.corp.l**t.net Unknown
     dc1nylv.l**t.com Unknown
    Alias (CNAME) and glue (A) records for forest GUIDs from server:
     CNAME: <My GUID>._msdcs.corp.l**t.net
    Alias: dc1ny.corp.l**t.net
    Glue: 172.16.0.4
    CNAME: <My GUID>._msdcs.corp.l**t.net
    Alias: dc1nylv.l**t.com
    Glue: 172.16.0.20
    CNAME: <My GUID>._msdcs.corp.l**t.net
    Alias: dc1nylvps.l**tp**g.com
    Glue: 172.16.0.21
    CNAME: <My GUID>._msdcs.corp.l**t.net
    Alias: dc1phx.corp.l**t.net
    Glue: 172.17.0.3
    CNAME: <My GUID>._msdcs.corp.l**t.net
    Alias: dc1phxlv.l**t.com
    Glue: 172.17.0.12
    CNAME: f<My GUID>._msdcs.corp.l**t.net
    Alias: dc1phxlvps.l**tp**g.com
    Glue: 172.17.0.13
    Total number of CNAME records found on this server: 6
    Total number of CNAME records missing on this server: 0
    Total number of glue (A) records this server could not find: 0
    DNS server: dc1phx.corp.l**t.net
    IP Address: 172.17.0.3
     UDP port 53 responding to queries: YES
    TCP port 53 responding to queries: Not tested
    Answering authoritatively for domain: YES
    SOA record data from server:
     Authoritative name server: dc1phx.corp.l**t.net
    Hostmaster: hostmaster.corp.l**t.net
    Zone serial number: 134
    Zone expires in: 1.00 day(s)
    Refresh period: 900 seconds
    Retry delay: 600 seconds
    Default (minimum) TTL: 3600 seconds
    Additional authoritative (NS) records from server:
     dc1ny.corp.l**t.net Unknown
     dc1nylv.l**t.com Unknown
     dc1phxlvps.l**tp**g.com Unknown
     dc1phx.corp.l**t.net Unknown
     dc1phxlv.l**t.com Unknown
     dc1nylvps.l**tp**g.com Unknown
    Alias (CNAME) and glue (A) records for forest GUIDs from server:
     CNAME: <My GUID>._msdcs.corp.l**t.net
    Alias: dc1ny.corp.l**t.net
    Glue: 172.16.0.4
    CNAME: <My GUID>._msdcs.corp.l**t.net
    Alias: dc1nylv.l**t.com
    Glue: 172.16.0.20
    CNAME: <My GUID>._msdcs.corp.l**t.net
    Alias: dc1nylvps.l**tp**g.com
    Glue: 172.16.0.21
    CNAME: <My GUID>._msdcs.corp.l**t.net
    Alias: dc1phx.corp.l**t.net
    Glue: 172.17.0.3
    CNAME: <My GUID>._msdcs.corp.l**t.net
    Alias: dc1phxlv.l**t.com
    Glue: 172.17.0.12
    CNAME: f<My GUID>._msdcs.corp.l**t.net
    Alias: dc1phxlvps.l**tp**g.com
    Glue: 172.17.0.13
    Total number of CNAME records found on this server: 6
    Total number of CNAME records missing on this server: 0
    Total number of glue (A) records this server could not find: 0
    Legend: warning, error
    DNSLint developed by Tim Rains

  • Server error - HELP!

    My server fine this morning...
    All of a sudden users can't login - GW POA shows LDAP error 81
    Rebooted Server and I get the following
    "error:NWDSRead Failed while reading a multivalued attribute: -603"
    Ran DSRepaire - NO problems.
    Googled the error but seems to suggests a DHCP/DNS error
    Not using either on the server
    I'm using a ISP's Server for DNS
    HELP!!

    Use LDAP is ticked but no server specified
    Tried Selecting the server but no effect
    Every where I look in POA, Domain setting its set to the SERVER's IP address
    not DNS name!!
    Copied NAMED.NLM (just the NLM) from SP5 server - error gone but still get
    the LDAP error 81 when a
    user tries to login to GW.
    I also POA > Security - I tried setting security to LOW (which unticks LDAP)
    but still can't login
    "Anders Gustafsson" <[email protected]> wrote in message
    news:[email protected]..
    > Eric,
    >> "Starting eDirectory integrated Novell DNS Server...
    >> error:NWDSRead Failed while reading a multivalued attribute: -603
    >> Loading the configuration and zone data completed .
    >> DNS Server running "
    >>
    > OK. I assume that you have configured your POA to use the same server for
    > LDAP. If so, did you use the DNS name or IP address? If DNS name, I
    > suggest you try IP address as this takes DNS out of the picture.
    >
    > The error you are seeing indicates that you are not current on servicer
    > packs:
    > http://www.novell.com/support/search...200%2043955231
    >
    > I suggest you apply SP6 plus the post SP6 fixes after resolving your POA
    > issue and reading this:
    > http://wiki.novell.com/index.php/Nw65sp6
    >
    > - Anders Gustafsson, Engineer, CNE6, ASE
    > NSC Volunteer Sysop
    > Pedago, The Aaland Islands (N60 E20)
    >
    > Novell does not monitor these forums officially.
    > Enhancement requests for all Novell products may be made at
    > http://support.novell.com/enhancement
    >
    > Using VA 5.51 build 315 on Windows 2000 build 2600
    >

  • IPhone connects to secured WiFi network, but can't access Internet

    Problem: iPhone connects to my secured home WiFi network, shows WiFi strength bars at top of screen, displays checkmark, lock, power, and blue arrow on WiFi Networks screen; however, cannot access Internet, iTunes store, stocks, Weather or anything else.
    Tests I've run:
    1. iPhone itself:
    ---DCHP:
    IP Address = 192.168.2.102 (within range automatically allocated by LinkSys router--see below)
    Subnet Mask = 255.255.255.0 (as per LinkSys router)
    Router = 192.168.2.1 (as per LinkSys router)
    DNS = 192.168.2.1 (confirmed by Apple as a valid DNS address given the above information)
    Tests:
    *Forget Network and rejoin--Failed to connect to Internet
    *Forget Network, reboot iPhone, and rejoin--Failed to connect to Internet
    *Reset Netowrk Settings and rejoin--Failed to connect to Internet
    *Reset All Settings and rejoin--Failed to connect to Internet
    *Deleted DNS entry--Failed to connect to Internet
    *Connect to Apple Store unsecured network--Success
    *Complete reset of iPhone at Apple Store:
    **Brought home, made no calls, did not sync with iTunes, did not reenter any info deleted by complete reset, joined network--Failed to connect to Internet
    **Synced data previously saved to iTunes, rejoined network--Failed to connect to Internet
    2. LinkSys router WRT310N:
    Tests:
    *Updated Router firmware--iPhone failed to connect to Internet
    *Entered a Static IP address on both router and iPhone--iPhone failed to connect to Internet
    *Reserved an IP within range automatically allocated by LinkSys router--iPhone failed to connect to Internet
    *Reserved an IP outside range automatically allocated by LinkSys router--iPhone failed to connect to Internet
    *Forced MAC filtering to use iPhone WiFi Address--iPhone failed to connect to Internet
    *Disabled all MAC filtering--iPhone failed to connect to Internet
    *Changed security settings:
    **No Security--Success
    **WAP Personal (AES)--iPhone failed to connect to Internet
    **WAP Personal 2 (auto selection AES or TKIP)--iPhone failed to connect to Internet
    **WAP Personal 2 (forced AES)--iPhone failed to connect to Internet
    **WAP Personal 2 (forced TKIP)--iPhone failed to connect to Internet
    *Changed security WAP Password/Passphrase:
    **10 characters (alpha numeric)--iPhone failed to connect to Internet
    **12 characters (alpha numeric)--iPhone failed to connect to Internet
    **10 characters (alpha numeric/ Uppercase alpha)--iPhone failed to connect to Internet
    **10 characters (alpha numeric/ Lowercase alpha)--iPhone failed to connect to Internet
    **10 characters (all numeric)--iPhone failed to connect to Internet
    *Set router to Mixed Wireless N/G/B Network Mode--iPhone failed to connect to Internet
    *Changed network radio band from Auto to Wide to Standard--iPhone failed to connect to Internet each time
    *Set router to Wireless G Only Network Mode--iPhone failed to connect to Internet
    *Changed Router IP address from 198.168.2.1 to 198.168.1.1 (LinkSys default)--iPhone failed to connect to Internet
    3. Microsoft router MN-500:
    Tried this old router (the one I used before purchasing the LinkSys). It is an old (circa 2002) Wireless B base station with WEP Security. The iPhone was never able to connect to the Internet using various settings, many of which were duplicates of the LinkSys tests above.
    On both routers my wife's Dell laptop and my HP printer connect without incident, using the same network/security settings.
    I have always been able to connect to various unsecured WiFi networks; I have never been able to connect to a secure WiFi network (although the only one I've really tried has been my own).
    I am at a loss as to what to do next. Any suggestions?

    SUCCESS!!!!!
    I visited my brother-in-law yesterday and attempted to connect with his secure network. By sheer luck, he is using the exact same model LinkSys router. My iPhone connected first time--so the iPhone was eliminated as a source of the problem.
    I didn't do a lot of troubleshooting at his house, but I did notice that his network was set for both dynamic DHCP and dynamic DNS. I know that either or both of Windstream (my ISP) and my broadband modem requires a pair of static DNS addresses.
    Sure enough, delving real deep into Windstream's support site, I discovered a LinkSys router DNS help page, specifying how to set static DNS addresses in LinkSys routers. I then accessed my router, enterd the known static addresses, saved the router settings, then rebooted the iPhone and connected to the network.
    SUCCESS!!!
    Thanks to Jane, who suggested it was an ISP issue, Jason, and all at Apple support. dumonj, I'll email you directly. Try this suggestion and see if it helps.

  • Macbook pro connects to iphone through bluetooth but can't access the internet

    Hello, I have a macbook pro 10.6 and an iphone 3gs 4.3.3. I used to be able to connect the macbook to the iphone through bluetooth using personal hotspot and access the internet but one day it just stopped working. I have tried turning them off and on, disconnecting bluetooth etc but nothing has worked so far. I have tried connecting my iphone to my ipad2 through bluetooth, it works great. The iphone to the macbook through usb and it works great as well. I have tried connecting another iphone to my macbook through bluetooth and it doesn't work. The bluetooth on my macbook seems to be the problem
    Well, to be more precise, the macbook sees the iphones, connects to them through bluetooth, the blue bar appears on the iphones screens but the computer wont access the internet.
    Any idea?
    Thank you very much.

    SUCCESS!!!!!
    I visited my brother-in-law yesterday and attempted to connect with his secure network. By sheer luck, he is using the exact same model LinkSys router. My iPhone connected first time--so the iPhone was eliminated as a source of the problem.
    I didn't do a lot of troubleshooting at his house, but I did notice that his network was set for both dynamic DHCP and dynamic DNS. I know that either or both of Windstream (my ISP) and my broadband modem requires a pair of static DNS addresses.
    Sure enough, delving real deep into Windstream's support site, I discovered a LinkSys router DNS help page, specifying how to set static DNS addresses in LinkSys routers. I then accessed my router, enterd the known static addresses, saved the router settings, then rebooted the iPhone and connected to the network.
    SUCCESS!!!
    Thanks to Jane, who suggested it was an ISP issue, Jason, and all at Apple support. dumonj, I'll email you directly. Try this suggestion and see if it helps.

  • Static IP address on iPhone

    Hi, and happy new year!
    I have a question for the community. I have just bought a Sonos music system. Every so often the controller on my iPhone loses connection with the system. I've done quite a bit of online research and the issue seems to be with how my router (at BT home hub) allocates and renews DHCP leases. I had a similar issue with my Samsung network printer which was resolved by setting it to a fixed IP address (so the router always assigns it the same IP).
    I'm gonna set fixed IP addresses to the Sonos components - but think the principal issue is the IP address assigned to the iPhone as this changes when I come and go from the house. I'm talking about the iPhones IP address on my home network, not on the cellular network.
    So my question is this... will setting a fixed IP address to the iPhone on the router (and on the phone) cause any issues I am not anticipating?
    I know HOW to do the IP address fixing - just not sure if I SHOULD.
    Thanks in advance - and if you have any other ideas for sorting the Sonos system, they'd me much appreciated.
    Chris.

    SUCCESS!!!!!
    I visited my brother-in-law yesterday and attempted to connect with his secure network. By sheer luck, he is using the exact same model LinkSys router. My iPhone connected first time--so the iPhone was eliminated as a source of the problem.
    I didn't do a lot of troubleshooting at his house, but I did notice that his network was set for both dynamic DHCP and dynamic DNS. I know that either or both of Windstream (my ISP) and my broadband modem requires a pair of static DNS addresses.
    Sure enough, delving real deep into Windstream's support site, I discovered a LinkSys router DNS help page, specifying how to set static DNS addresses in LinkSys routers. I then accessed my router, enterd the known static addresses, saved the router settings, then rebooted the iPhone and connected to the network.
    SUCCESS!!!
    Thanks to Jane, who suggested it was an ISP issue, Jason, and all at Apple support. dumonj, I'll email you directly. Try this suggestion and see if it helps.

  • Yahoo domain and .Mac

    I have a question similar to one discussed here:
    http://discussions.apple.com/thread.jspa?threadID=1313370&tstart=135
    I have added a CNAME record and www.mydomain.com now forwards smoothly to the content I've put up on .Mac.
    However, mydomain.com does not. Yahoo only has an A record for the domain without www and it requires an IP address. Doing a DNS lookup on web.mac.com produces 17.250.248.34, however http://17.250.248.34 in a browser is much different from http://web.mac.com. Would that work??
    I thought of trying to put a Yahoo front page for mydomain.com with a Javascript redirect to www.mydomain.com, but sadly they don't allow Javascript (or even HTML markup for that matter).
    It also seems that the search engines visit the URL without the www, so this is seriously messed up.
    Thanks for any ideas!

    Help? Yahoo says to set up an A record, leave Source blank (_____.houseofbeing.com) and enter an IP address as Destination. I entered the IP address for web.mac.com: 17.250.248.34.
    Yahoo gave an error message:
    Warning: Some Advanced DNS configurations can disrupt your service. Please carefully plan your configuration. For more information, refer to our Advanced DNS Help pages.
    The record that you requested cannot be set up because it would otherwise interfere with DNS records Yahoo! has created to support your service. Please choose a different source hostname.
    Add an A or CNAME Record
    Enter a hostname in the "Source" field. To create an A Record, enter an IP address in the "Destination" field. To create a CNAME, enter a hostname as a destination instead.
    Note: Any changes you submit will take 30 minutes to take effect.
    Source: _______.houseofbeing.com
    Hint: Enter "info" to create the hostname info.houseofbeing.com. To create an A Record for your root domain name, leave the Source field blank.
    Destination: 17.250.248.34
    Hint: For an A Record, enter an IP address, like 17.12.22.11. For a CNAME record, enter another hostname, like info.other-domain.com

  • RV320 and RV325 Feature Request

    Hello Cisco Small Business Community.  
    We are a Cisco Select Partner and have started using RV320's and RV325's with our customers.  As we are implementing these deployments, I have noticed there are a few features I would like to see added to the product.  I've listed them below.
    Urgently Needed Feature Requests:
    1.  Allow a subnet mask in the 255.255.0.0 range for LAN VLAN's.  Many of our customers use a 10.x.x.x range for subnets and many use a 16 bit subnet mask to give them plenty of room to create both static and dynamic assignments.  For example, subnet 10:  10.10.0.0/16 with a range of 10.10.10.1-254 for dhcp dynamic leases, and 10.10.0.1-254 for servers, and 10.10.1.1-254 for printers, and 10.10.2.1-254 for networking gear, etc.  None of these networks have more than 254 devices on them, but the extra IP range availability is nice because it allows us to help keep their networks organized.
    2. The ability to create service groups for firewall and NAT rule creation.  There are often times when we need to group several services together and create firewall and NAT rules for them.  This would simplify setup and implementation.  An example of this feature on Cisco Small Business Products was on the ISA550.
    3.  The ability to have the RV320/325 to serve as the NTP server for the network.  Most small business customers need NTP server functionality, and the logical place to stick this service for many of these networks is on the firewall.
    4.  The ability to specify any RFC DHCP option.  We have some need to be able to specify several additional DHCP options than the ones hard coded into the firewall dhcp server pages.  In addition to the options the DHCP servers on the RV320/325 already includes, the common ones that we often use are "Time Server," "Log Server," and "Time Offset."
    6.  The ability to specify a domain search list and for DHCP clients.
    7.  The option to register DHCP clients with the specified DNS server (including the on-box DNS Forwarder).
    8.  The ability to tweak Firewall Session Settings (like in the RV220w and ISA550) and TCP/UDP Timeouts.  If full control is not an option, then may four choices such as:  "Conservative" -- keeps TCP/UDP connections alive for the longest period of time, "Normal" -- normal TCP/UDP Timeouts, High Latency -- Keep TCP/UDP connections alive for a longer period of time.
    9.  Additional Diagnostic/status screen information:  -- CPU usage for 1 minute, 5 minutes, and 15 minutes, -- number of Firewall Sessions/States, --Firewall Temperature, -- Real Time and RRD based traffic graphs for 15 minutes, 4 hours, 8 hours, 1 day, and 1 week, 
    10.  The ability to pull Firmware Updates directly from the Cisco support site onto the firewall.
    Nice to Have Features:
    1.  VRRP on both WAN and LAN interfaces.
    2.  The ability to answer DNS helper requests.  What I mean is to be able to set the on-box DHCP server up to serve as the DHCP server for non-connected subnets
    3.  SSH and Telnet command line access for basic troubleshooting (top, pftop, nbtstat, reboot, etc.)
    4.  The ability to backup and restore parts of the Config file, e.g. just the VPN setup or just the firewall rules
    5.  OSPF Dynamic Routing Support
    With some of the advanced features, I wouldn't mind needing to buy a perpetual "advanced" license for an extra $50 to $100 (e.g. for VRRP, OSPF, SSH access, etc.).
    I hope to hear some responses back from Cisco Product Support on these items. 

    Hello vreid47362,
    I'm quite a bit surprised to see that we have both the same idea: provide our feedbacks to cisco to increase our product usage.
    Here's mine list:
    Custom services
    - I was a bit surprised when I have seen for the first time the embedded services list : there is some that I'm sure that nobody use (HTTP and HTTPS secondary), and some usefull network protocols which are missing : NTP, NNTP, NFS, SAMBA, BONJOUR, SSDP, etc.
    It could be interesting to start router with those embedded services.
    - An option to select both the TCP and UDP services could be very usefull : for now, when we add a service, we have to specify protocol in the following list : TCP, UDP, IPV6.
    If I wants to add a rule for NFS without take care of TCP and UDP, I have to set up :
    - two custom services, one for UDP, one for TCP
    - two custom rules, one for NFS TCP, one for NFS UDP.
    If we have two networks or VLAN, we have to define 4 rules...
    - Increase the custom service description length could be helpfull : for now it's a problem if we wants to add more than 11 characters.
    - If we add a custom service by error, we are unable to remove the generated field : field say that it expect something. if we do not wants to loose previous fields set, we have to save it with false values, and delete after it. Just boring. 
    Setting up firewall rules for the first time
    - The "View logs" button is located on the bottom of the log tab; if we wants to view logs, we have to scroll : it's very boring when we're setting up our rules : we have to go to the firewall tab, and if there is something wrong, we need to go to log tab and scroll.
    If you add a shortcut to the log from the firewall rules tab could be very usefull.
    Managing firewall rules on the time
    - Be able to add a description of the rules defined could be helpfull : I've set all my rules now, but in few months when I'll come back to the interface, I'm not sure to understand all meaning. A description to explain the rule's object could be usefull.
    - If we log something in the firewall logs and if we want to remove the a logging trace type, we have to pass on each rules we think it can log something. It could be interesting to view logging option from the grid: it'll help us to earn time.
    - Be able to filter rules by VLAN, protocol, ports or the rule's logging state from the rules grid could be helpfull.
    Double Wan management
    - Add an autodetect feature for the available bandwith could be very helpfull : accoding with values detected, you can help to configure more easily the router
    Double wan protocol binding and multiples VLAN
    - When I set up the protocols binding configuration I'm was very boring to have to set up rules for all outgoing protocol rules a interface : for example,  wants to set up all outgoing SMTP protocol on the WAN1 interface, we have to select SMTP and add 1.1.1.1 au 223.255.255.254. If we have multiples VLAN, we have to repeat this rule for each VLAN subnet mask…
    Set up an option for all outgoing traffic could be very helpfull.
    DHCP Subnet masks more than 255.255.255.x
    Like vreid47362 said, I'm also interested in this feature: For now, subnet masks defined for the DHCP Vlan are provided from a preconfigured select box. If we wants to choose something other than those provided, we can't. It could be interesting to add own own subnet mask (like for example 255.255.0.0).
    Kind regards
    David

  • Safari cannot find server-any other browser can

    Recently Safari started telling me that it cannot load webpages because the server cannot be found. Any other browser can load these pages correctly.
    The webpages that Safari picks out are completely random and change from day to day.

    I had the same problem, made a little search and found that there are some problems with DNS on leopard if you´re interested to know a little try this page:
    http://blog.jungledisk.com/2007/10/31/leopard-dns-issues-and-work-around/
    changing the DNS helped me a lot so try this to have a better way to improve your safari experience:
    http://www.macfixit.com/article.php?story=20070416000657464
    hope this will help you

Maybe you are looking for