Changeip ****

I get an error -14008 (opening node) after this command
changeip /LDAPv3/127.0.0.1 144.163.aaa.bbb 144.163.aaa.bbb badname.com goodname.com
I upgraded this X Serve G5 to 10.4.11 and the old name some how remained,
also Open Directory has a problem, I can't stop the service. It is set to Stand Alone
Thanks

The changeip command will not change the ip address.
Use networksetup or serversetup or Network Preferences in order to change the ip and other network settings.

Similar Messages

Mac OSX 10.5.3 Leopard STANDARD Server CHANGEIP questions

I am confused on how to check and change TCP/IP addresses via Mac OSX Leopard 10.5.3 server in STANDARD mode.
I watched the great Sean Colins Lynda.com tutorial on OSX 10.5 Server, but i still have a few questions with how to deal with DNSs and CHANGE IP
Here is the hardware & scenario:
-- G5 Silver Doors Tower with 1.7GB Ram and Mac OSX 10.5 Leopard 10 user server
-- Cablevision ISP with there BOOST service [that allows you to set-up a server and does not block ports 25 or 80]
-- NO Static IP from Cablevison [they change it once in a blue moon when they want so I rely on DYNDNS below]
-- Apple Airport TimeCapsule [with all latest firmware updates etc]
-- DynDNS account and client software installed on server to update the DYNDNS severs with the current Cablevisions TCP/IP address
Problem and Question
===
Three times a year I will need to move this server. 1/3rd of year and at setup it is on residential Cablevision Account and Apple TimeCapsule Router, Then 2/3 of year server will be behind two funky large networks where I will have to set-up manual IP, DNS, and proxy info
I need to know what the proper process is when I want to move the Mac. When the 10.5.3 STANDARD Server is in STANDARD mode can I just change the TCP/IP address in SYSTEM PREFERENCES...NETWORK ? Do I have to run the CHANGEIP command Afterwards [or Before]
Also, for DNS config on server does it always need to have the loop back self reference [127.0.0.1] or can it just be configed from the Airport and/or network?
And, big problem for now... dumbly when I set-up the OSX Server on the TimeCapsule Network I forgot to write down the TCP/IP address used. Now I am on the second funky corporate network and can't use the command:
sudo changeip - idon't_knowip 10.0.96.48 server.cmtenyoffice.com server.cmtenyoffice.com
Also, another question for the HOSTNAME... should it be HOSTNAME or FullyQuallifiedDomainName?
My HOSTNAME seems to be "CMTE-Server.local" but I specified the FullyQualifiedDomainName to "sever.cmtenyoffice.com"
NOTE: I do NOT have this domain registered and am not yet hosting a website or email server on this machine, but I may soon register the domain and then point MX records etc to the DYNDNS record that would point to server
Anyhow, to wrap up,
1- What is the proper process for changing the TCP IP address with a Leopard 10.5.3 STANDARD SERVER?
2- What do I do with CHANGEIP command if I don't know what the STARTING TCP/IP address is?
3- For HOSTNAME should I be entering the unregistered FQDN or the "CMTE-Server.local"
Thanks for any an all info.
-- Eric ZORK Alan
-- Professional Poet & BED VLOGGER

Hi Eric
You use the one its using now.
If the Server is Standalone issue:
sudo changeip - oldIP newIP oldhostname newhostname
Even if nothing changes you can still issue the command, supply the system admin name and password and let it do its stuff. Prior to doing this you must change the address in the Network Preferences Pane. Although not necessary it does not hurt if you restart afterwards.
If the Server is an OD Master issue:
sudo changeip /LDAPv3/127.0.0.1 oldIP newIP oldhostname newhostname
You will not only be prompted for the system admin name and password but also for the Directory Administrator name and password. With both command you will get feedback as to what is going on. Obviously you will see more changes made if its an LDAP Server. Hostname will be the fully qualifed domain name (FQDN) defined in the DNS Service eg: myserver.mydomain.com.
man changeip
For usage. Actually prior to doing any of this and incidentally a good way of finding out not only the hostname but also the IP address associated with that name issue:
sudo changeip -checkhostname
You should run this before/after making the change. If everything checks out OK it should report 'the names match, there is nothing to change'. This is a good a test that lets you know its worked. However its not the only test. I would run host, nslookup and dig also. Next set a client to use the Server for its DNS and then test connectivity with firstly the Server's fqdn and lastly its IP Address.
Ultimately the truest test is: "what impact has the change made on clients accessing the Server and its Services successfully?"
If the Server is a mature OD Master (possibly PDC as well) with DNS, Mail, AFP, SMB, iCal and any other 2-3 additional services configured and running then issuing changeip may appear - superficially - to have worked. Occsasionally - in my experience - serious problems begin to develop with the LDAP database to the extent where the only 'cure' is to demote to Standalone, sorting out DNS and re-promoting. This can have serious repercussions if you have not made preparations to limit the re-build time prior to changing the IP address and issuing the command. Equally it can be successful. However can you take the risk?
Tony

Changing hostname beyond changeip

I'm trying to get the hostname changed on my server after doing a fresh install with 'macsrv1.local' as the initial hostname.
Doing changeip worked to change 'macsrv1.local' to 'macsrv1.domain.com' so that 'uname -a' reflects the new fqdn. My dns entry is fully under my control and has a proper reverse lookup record.
What I can't figure out is how to get the gui to reflect the new domain. Server admin shows local hostname as 'macsrv1.local' and under System Preferences - Sharing, using the edit button gives me a fqdn with the '.local' greyed so that I can't modify it.
What am I missing?

Hmmmm.. After talking to XServ support on the phone, I understand the distinction of .local
New to me - any OSX computer will show up with .local in server manager and this is functionally equivilant to 'loopback' or 127.0.0.1
No longer a problem.

Changeip question...

hi...
i need to change the subnet of my xserve... i presume i need to do so using the changeip command but i found this post
http://www.afp548.com/forum/viewtopic.php?forum=18&showtopic=12944&highlight=cha ngeip...
is that still accurate? if so, how does it work?
if its not the case, and i need to use changeip, are there any specific ways to do so? ie:
do i need to unplug the server from the network first?
do i need to remove its entry from the DNS server first?
if i'm not changing the host name, do i need to put it in the changeip command?
once i've run the changeip command, and changed the ip in network settings, do i need to reboot the server?
how can i check that the change of ip was 100% successful?
ah i nearly forgot, how does it apply when your xserver has 2 network cards?
thank you
Mac OS X (10.4.9)

Hi:
You should be able to do this on a live server with no repercussions as the article in the link suggests. You are not changing the ip address as such, just the sub-net mask.
Regardless of whether you are using one or both NICs it wont matter either way if all you are doing is changing the sub-net mask on both NICs. However if you are using both and depending what services you are providing it could have repercussions. You have not gone into any detail regarding this. It cant hurt restarting the server.
You will have to make allowances for sub-net mask changes if you are hosting DHCP Services. Stop the DHCP Service first, make the changes in the Network Control Panel as well as DHCP Service then restart the server, after log-in restart the DHCP Service. DNS Service does not take account of the sub-net mask so this should not be affected.
As always make sure it is only the sub-net mask you are changing as well as having a fallback position in case it all goes wrong; ie: a full working backup.
Hope this helps – Tony

Changeip command? Trying to view or change the DNS name of a computer.

Hey guys, I did a time machine on computer but it is still remembering the old DNS name.
I looked it up and it looks like you can use the changeip command to change the DNS name but when i try and run the command it says changeip command not found.
Any ideas?
Thanks!

Hi
Apple have changed (sic) the changeip command. In 10.6 Server it now does not have the same functionality it used to have in previous versions. Reason being it was not always successful in doing what it was supposed to do. To change the hostname use scutil:
sudo scutil --set HostName thenameyouwant
The changeip command does not exist on the client OS.
Tony

How does changeip determine the dns hostname?

Hello,
i've been trying to setup my 'test' server at home according to the info i find online.
one of the first parts is setting the hostname. It is recomended that you use something like
server.myowndomain.com
when i use sudo changeip -checkhostname i get
Primary address     = 192.168.xx.xx
Current HostName    = server.myowndomain.com
DNS HostName        = myowndomain.com
To fix the hostname please run changeip for your system with the
appropriate directory with the following values
   /Applications/Server.app/Contents/ServerRoot/usr/sbin/changeip 192.168.xx.xx 192.168.xx.xx server.myowndomain.com myowndomain.com
dirserv:success = "success"
at my external dns control panel there are 2 A records for my domain name
localhost
A
127.0.0.1
server
A
78.xxx.xxx.xxx
when i ping from a remote location i get results for both myowndomain.com and server.myowndomain.com
i had my server working when i used myowndomain.com as hostname, but everywhere i read it says you should use something like server.myowndomain.com as a hostname.
Is there an other tool i can use to check what dns hostname i'm having?
can someone shed some light on this for me please?
thanks
Marco

If you are setting up your server on your LAN, then you need to support what is called split horizon DNS. This means that you need to run a public DNS (which you have based on the ("at my external dns control panel there are 2 A records for my domain name") and you must run DNS on your LAN as well. The reason for this is simple.
When running your server on a LAN behind a firewall, your server has two identities. The first identity is its LAN address. As above, this is something on the 192.168.x.x network. This is a private address range and can not be used for public routing. The second identity is that of the public Internet. As above, this is represented by the 78.x.x.x address that is the public address used by your firewall.
When users on the LAN reference your server, they will need to reference it by the 192.168.x.x address. When users externally want to access it, they will need to route to the 78.x.x.x network. Thus, the need for two DNS entries.
Now, the DNS entries are commonly the same. The difference is the number assigned to the record. For example, server.myowndomain.com will point to 192.168.x.x on your LAN and server.myowndomain.com with point to 78.x.x.x on the WAN.
Other ways to check DNS would be to use nslookup or dig. Also, check the server's network preference panel and look at your DNS entries. The first entry should be a 192.168.x.x address and it should be pointing to a DNS server on your LAN. This could be you server or it could be another device that is already running DNS.
DNS is considered the foundation service for OS X Server. However, it all depends on the services that you are running. For Open Directory, Profile Manager, and others, DNS is critical. Failure to implement it properly will give you nothing but headaches and likely cause future service deployment issues. However, if you are just hosting a bunch of web sites, then DNS is not as critical, especially if the server is deployed on a LAN with no clients.
As a note, if you were running your server with a public address, you could use BIND views. However, this is not advisable for security reasons.
R-
Apple Consultants Network
Apple Professional Services
Author "Mavericks Server – Foundation Services" :: Exclusively available in Apple's iBooks Store

Actiontec MI424WR-GEN3I with ChangeIP dynamic dns

I'm trying to configure my router (Actiontec MI424WR-GEN3I, v. 40.21.10.3) with ChangeIP.com dynamic DNS. It's listed in the provider drop-down in the Dynamic DNS section of the router GUI, so i figured i'd be all set. I setup an account with ChangeIP, and then got a hostname from them.
In the router i'm configured as follow..
Hostname: MyHost.changeip.com (<-- actually MyHost.onmypc.org; "onmypc.org" being one of the domains ChangeIP offers for free.)
Connection: Broadband Connection (Ethernet/Coax)
Provider: changeip.com
Username: My changeip username
Password: My changeip password
Dynamic DNS System: Dynamic DNS
Offline: (not checked)
SSL Mode: None
In the status area it just says "Error - Unknown changeip.com error". There's nothing in the changeip knowledgebase. Has anyone tried configuring changeip on their router? I know they have something called homeing beacon, but really i just want this to work as configured without having to install anything extra.
Thanks!

Hello, I had the exact same problem. It seem Verison FiOS router is not very flexible. You can't enter another Dynamic DNS (DDNS) and can only use one on the list. The only two free one I found was no-ip.com and changeip.com.
The no-ip.com came back with a host not found cause they've changed the name to noip.com (without the dash) so the dumb router is not able to find it.
The changeip.com is no help either as you've found out. I keep getting Error but it does not say why. Fortunetely I did found a solution. You can download changeip.com's DDNS Update Client (for Windows, Linux, or OSX). The called this software as Homeing Beacon.
http://www.changeip.com/accounts/downloads.php
In Windows it runs as a self startup service so you don't to remember to run it but you will need a Windows PC to be on for the update to occur. Basically instead of updating changeip.com's DDNS entry from the router, you have a Windows client that somehow figures out what the router's IP and act as a proxy agent and update your DNS entry on changeip.com. This is a workable workaround, I think. The drawback is you need a PC running every so often on your home network so updates occur. But, the price is FREE and you can't beat that.

LDAP + create homedir after changeip failure

Hi all
I have a vertically mounted Xserve running 10.4 and have some troubles.
When I tried using changeip to change the server name of my xserve things started to become funky. This is what I did:
* saw errors about DNS name in log
* added the server name in DNS forward and backward
* copied the changeip command line that I got from it.
* didn't manage to insert the password for diradmin (not sure about this)
So I wonder what kind of trouble I have gotten myself into.
Everything seems to be working, except I can't click "Create home now" in Workgroup manager. I can create the home dirs manually from the shell, like this:
mkdir /Users/new_user
chown newusername /Users/new_uesr
Does anyone know what Workgroup manager does when I click that button?

Of course I have a backup of the server state before I did this, but I don't know what to restore or what to compare..

Please help wth a 'changeip' error

Hey
We have just recently been turfed out of our office and relocated to different building. Our IT dept has informed us we need to change our servers IP address as they now need that for something else.
I have done as much research as I can and looked through countless discussion posts and manuals and have come to the conclusion that I have to use a command in terminal called 'changeip' reading furthur I believe I must also add 'sudo' the the start of this so that I am logged in as root.
our current IP address is : 172.16.64.10
and we need to change it to: 172.16.32.5
now as far as im aware my command should therefore be :
sudo changeip /LDAPv3/127.0.0.1 172.16.64.10 172.16.32.5
This doesn't seem to work however. I do get a prompt for a password then I get the error:
'DNS doesn't not have a valid name for IP address 172.16.32.5
If DNS is not repaired, errors will be logged and functions will not work properly'
now I have just found a page saying that with servers running 10.4.6 or over (which we are) I must now "now use a fully qualified domain name (FQDN) with the command."
I found this at :
http://docs.info.apple.com/article.html?artnum=303495
To be honest im not exactly sure what this means, but the differences I see is that they include'testserver.example.com testserver2.example.com' after the IP addresses in the command.
In DNS on our server I believe our dominan name is:
medusa.filton.ac.uk
My question is: does anyone out there think I have to enter this in my command or change something in DNS first so that my command functions.
Im basically looking for a guide to getting this IP swapped so I can start getting my macs back online and seeing the server again. From what i have read it should be reletivly simple or running the correct command and then going to network prefs and swapping them manually and restarting.
This as I feared is not the case
Any help would be greatly appreciated
Thanks
Ryan

I have checked with the IT bobs downsatirs and they do confirm that the IP does indeed have forward and reverse DNS lookups
That's a bit murky, so let's confirm, shall we?
Open Terminal and try the following:
dig medusa.filton.ac.uk
dig -x 172.16.32.5
dig -x 172.16.64.10
If it's as they say, the replies should be, in order as above:
172.16.32.5
medusa.filton.ac.uk
medusa.filton.ac.uk
Although the last answer is not entirely necessary to the exercise; they may have already re-assigned the old IP address. If it's different, note it and use it in the changeip command, like so:
changeip [(directory|-)] old-ip new-ip [old-hostname new-hostname]
Which reminds me of a few things:
1) I got this out of the following manual:
<http://images.apple.com/server/pdfs/CommandLine_v10.4_2ndEd.pdf>
and it bears reading through every mention of the changeip command. (As well as, if so equipped, the code itself; see p. 66.) See p. 67 for a walkthrough of the procedure.
2) The first argument ("directory") is important and you need to make sure it's correct for your network config.
3) I've only used the command a few times myself, but I remember having to try it a few different ways, especially for the "directory" argument.
- Marc

Changeip not working?

I recently did a change of IP on my Xserve G5 running Tiger 10.4.5.
Two days after changing the IP in System Preferences, I used changeip like this:
sudo changeip /LDAPv3/127.0.0.1 201.224.xxx.116 201.226.xxx.162
I now CAN'T login as any Open Directory user. Even after running the changeip command. I tried changing the homes directories (which were binded to afp://201.224.xxx.116) to the new ip, but I still can't login.
Some help would be really appreciated.

When you say you "can't login" , do you mean: as a user at a client machine, attempting to authenticate to the server ?
Thre things come to mind: did you use Directory Access on the client Macs, to change the info to point to the new IP ? If you originally configured this by hostname, launch the Terminal application, and check:
dig your.servers.fqdn
what does that get for an answer, when you try that on a client Mac ?
Where your.servers.fqdn is your server's full DNS name, eg:
server.nutsnbolts.org
You may need to run: sudo lookupd -flushcache
on the server and clients.
Which leads me to: are you running DNS on the server, or is it fully hosted elsewhere ? Did the DNS records get changed to reflect the new IP ?
What does
dig your.servers.fqdn
and
dig -x 201.226.xxx.162
tell you ?
Do of course use your actual (full) IP there, not with the "x"-es

What is 'changeip'. how do I use it?

I have just set up a MacPro with dual NIC's and followed Apple's recommended install of having a modem/internet on en0 and switch/LAN on en1. During the install process I did as requested and entered out ISPs settings on en0 and progressed with the rest of the install. I have DNS errors, and also keep seeing our ISPs (instead of our server's) details showing up through the server in places like sharepoints.
Searching the threads here I see members with similar problems who are being told to use 'changeip'.
I am a complete newbie, I don't understand commandline. What I'm looking for is a basic 'do this, then this' type response to help make our server happy.
Here's the error:
Aug 8 08:19:27 xserver servermgrd: servermgr_dns: configured name and reverse DNS name do not match (xserver.local != dsl-217-155-192-186.zen.co.uk), various services may not function properly - use changeip to repair and/or correct DNS
Aug 8 08:19:48 xserver servermgrd: servermgr_dns: no name available via DNS for 192.168.2.1
Aug 8 08:19:48 xserver servermgrd: servermgr_dns: no reverse DNS entry for server, various services may not function properly
Can anyone shed any light here please?

No, Apple doesn't recommend that as a "always do this" procedure. What was your specific goal ?
Especially if you're completely new to this, let your router take care of NAT for you.
With all due respect your company should consider hiring someone, there are too many things you need to learn all at the same time. If you were tasked with driving a bus for a company event, you'd decline if you'd never driven manual transmission before, let alone lacked a driver's license (and experience) qualifying you to drive a bus.
Start by reading through Apple's server documentation.
Next, "google" for bash/shell tutorials, there are many.
Here's one
http://developer.apple.com/documentation/OpenSource/Conceptual/ShellScripting/in dex.html
For anyone wanting to manage a server, be it Apple's OS X or other bsd/unix/linux OS, knowing the "commandline" is an essential part of your toolkit.
I do mean essential.
With OS X Server, command-line ability will often allow you to make a quick fix where without it you'd be faced with a wipe-and-reinstall.
At this point, you may do best to do just that, after re-planning your server configuration and learning some DNS fundamentals.
http://www.oreilly.com/catalog/dns5/
http://www.zytrax.com/books/dns/ch1/
OS X Server must have working forward and reverse DNS entries for its FQDN. You don't have to run DNS on your OS X Server itself if you have existing DNS servers.

Use of changeip

Hi there
I am switching ISP soon so the external servers need an IP address change which of course is done with the CLI changeip. I have also decided to reconfigure the LAN, moving away from 192.168.1.x to avoid clashes with other networks through VPN connections. Assume I also use changeip for this. Rather obvious question I guess, just don't want to muck up the IP changeover at the time.
Thanks in advance.
Cheers, Paul

Google can often be your friend here. Google for +site:discussions.apple.com changeip+ or such -- the Google site: keyword is a very useful feature for targeting your query. There have been some changeip discussions here, as changing an IP host address is a fairly common task, as Mac OS X Server management goes.
The manuals can be your friend, too. There's also a section in the [Leopard Command Line Administration manual|http://images.apple.com/server/macosx/docs/CommandLine_Adminv10.5.pdf] containing a changeip sequence around page 68. This covers some details.
The manual goes into some detail on the specific sequence for changeip, and it's the canonical source for this and many other command sequences, and for related considerations (the sort of ancillary details that tend to get missed in forum discussions) such as the potential need for DNS changes.
And if you don't have a full disk utility disk copy or other such archive handy, having that in place might be a good idea before you wade into any sort of serious system reconfiguration. That'll allow you to recover from errors, in the (very) unlikely event something fails.
Might want to get a static IP and a DNS entry from your provider, too, as it looks like you might have a dynamic DHCP address here.

Changeip hostname to name.local rendered server inaccessible most of the time

I followed the instructions here:
http://maymay.net/blog/2007/09/19/changing-the-hostname-on-mac-os-x-server/
According to Apple, I also have to change the hostname somewhere else.
http://support.apple.com/kb/TA24015
"Before running changeip, be sure you have updated the server's hostname in DNS to match the hostname provided to changeip; otherwise errors will be logged in system.log, and services may not function properly".
I am not if you have followed my plight before currently running DNS so I changed it as described in the blog post above to be the bonjour name. Sometimes I can access it at [email protected] On some computers 100% of the time, and on some computers not at all. This may very well have to do with whether or not they are on the same subnet.
What I'm wondering is did I use the changeip command correctly, or should the unix name be separate from the bonjour name? When I first set it up, it seemed to function once I enabled DHCP. I was trying to solve a daylite problem originally. c'est la vie.
I am primarily trying to use it as a local file server/daylite server. Daylite mostly functions, while the file server does not. I hope this isn't extraneous information. Probably I need to access it via IP?
I'll post the original Daylite KB article if that would be useful to you.
--Sam

You can use both Bonjour (multicast DNS) and traditional DNS (unicast DNS) together. Your clients can use your own DNS server to access LAN-local services, and Bonjour where that's appropriate (eg: client to client, server to client, etc).
To do the internal and external demarcation, register two domain names. I usually use different TLDs on the same domain, and registering and holding a few extra of these domains means you won't have "fun" later, as the DNS namespace continues to fill up.
You can then use the external domain name for hosted mail services and stuff that's accessible outside your LAN, and that'll be the domain name that's listed in the hosting service's or your ISP's public-facing DNS.
Your internal network uses your own DNS server, and your DNS server then provides translations for your static-addressed devices on your network (eg: network printers, your external gateway-router-firewall device, any NAS devices, your Mac OS X Server box, etc), are referenced in your local DNS using your internal domain name. Your internal domain name and your local host translations are all used within your private DNS server configuration, and the translations are not accessible outside your LAN; you need to be connected to your LAN directly, or via VPN.
Using the two domain names means you don't have to manage the same domain name for both internal and external sites, and the external DNS services. You're managing two separate and non-overlapping domains this way, rather than one domain name that has two seperate and authoritative servers active.
There's a whole lot more detail in that DNS article you're probably reading by now, too.

Changeip -checkhostname

Hi !
I have an Apple Intel Xserve running 10.4.11
It is a fileserver but is also running its own DNS
I am seeing the following in the logs
Feb 2 09:07:30 fileserver servermgrd: servermgr_dns: gethostbyaddr() and reverse DNS name do not match (fileserver != fileserver.company.org.uk), various services may not function properly - use changeip to repair and/or correct DNS
However if run
changeip -checkhostname
dig -x 192.168.2.11
dig fileserver.company.org.uk
(see below)
All the responses - appear to be correct -
So how can I stop these error messages without amending /etc/hostconfig which I believe you are not supposed to do.
fileserver:~ root# changeip -checkhostname
Primary address = 192.168.2.11
Current HostName = fileserver.company.org.uk
DNS HostName = fileserver.company.org.uk
The names match. There is nothing to change.
Also
fileserver:~ root# dig -x 192.168.2.11
; <<>> DiG 9.3.6-APPLE-P2 <<>> -x 192.168.2.11
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 14292
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1
;; QUESTION SECTION:
;11.2.168.192.in-addr.arpa. IN PTR
;; ANSWER SECTION:
11.2.168.192.in-addr.arpa. 86400 IN PTR fileserver.company.org.uk.
;; AUTHORITY SECTION:
2.168.192.in-addr.arpa. 86400 IN NS fileserver.company.org.uk.
;; ADDITIONAL SECTION:
fileserver.company.org.uk. 86400 IN A 192.168.2.11
;; Query time: 1 msec
;; SERVER: 192.168.2.11#53(192.168.2.11)
;; WHEN: Wed Feb 2 09:10:03 2011
;; MSG SIZE rcvd: 112
AND
fileserver:~ root# dig fileserver.company.org.uk
; <<>> DiG 9.3.6-APPLE-P2 <<>> fileserver.company.org.uk
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30191
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;fileserver.company.org.uk. IN A
;; ANSWER SECTION:
fileserver.company.org.uk. 86400 IN A 192.168.2.11
;; AUTHORITY SECTION:
company.org.uk. 86400 IN NS fileserver.company.org.uk.
;; Query time: 0 msec
;; SERVER: 192.168.2.11#53(192.168.2.11)
;; WHEN: Wed Feb 2 09:10:24 2011
;; MSG SIZE rcvd: 73

how can i fix this problem?
Unless i'm missing something - all you need to do it correct the DNS server so that the forward and reverse records match the name of your server.

DNS set up

I have problem setting up a correct DNS. This is a possible cause Open Dir doesn't work, in-fact I'm unable to create an Open Directory Master; while all the other services (web, mail, ical) work fine.
The server name on ServAdmin top left side is macweb.local; the machine IP is 192.168.115.24.
From term the command changeip -checkhostname, prompts the following:
"Primary address = 192.168.115.24
Current HostName = macweb.server.com
The DNS hostname is not available, please repair DNS and re-run this tool.
dirserv:success = "success""
So far I created under the DNS function of ServAdmin a primary zone with:
zone name=server.com
nameserver-hostname (fqdn)=macweb.server.com.
Then a record machine named=macweb
with two IP addresses under it: 127.0.0.1 and 192.168.115.24
obtaining two reverse zones mapping macweb.server.com on the two ip.
Re-running the changip command the result doesn't change.
Any suggestion is very well appreciated.
Alberto.
Message was edited by: albfran
Message was edited by: albfran

[Here is a DNS server set-up sequence|http://labs.hoffmanlabs.com/node/1436]. That's end-to-end.
Are you strictly referencing this DNS server from your LAN and from your DHCP server, or are there references to any other DNS servers mixed here?
Assuming your server here is your DNS server, is your DNS server here referencing itself (in the guise of the 127.0.0.1 loopback address) via System Preferences > Network controller > static IP, static DNS server setting? Or is it referencing some other DNS server?
Your other clients on your LAN can refer to your DNS server via its static IP address, but the DNS server here should use the loopback address.
Post the output of the Terminal.app commands +dig server.example.com+ and +dig -x server.ip.address.here+ in its entirety, and I'll have a look at the data returned. (If you want to obfuscate your domain there, that's fine, but don't obfuscate the 192.168.0.0/24 addresses anywhere in what's returned, and the obfuscation of the host names needs to be consistent for the output to be useful in diagnosing this.)
And FWIW, you probably aren't the organization that has registered the server.com domain name, so please stop using that domain either for real in your configuration, or using it as your example domain name. If your intent is to obfuscate your domain name (and which is fine by me) then use example.com, example.net or example.org as your domain name. These are RFC-reserved example domains. This usage both avoids referencing a domain you don't have registered, and it makes your intent here clear. It means I don't have to ask you "is that your real domain, or are you obfuscating?".

Changeip ****

Similar Messages

Maybe you are looking for