Quick and Simple DNS Config

Hello,
I have a Mac Mini Server 10.6.4 as a SUS on my internal network. I use DynDNS to reach my network from outside (servername.homeunix.com). I was wondering how I set up my DNS so that when my clients are on the internal network, servername.homeunix.com resolves to the INTERNAL (eg. 192.168.0.50) address. But also so when the client is outside the network, servername.homeunix.com resolves to the PUBLIC (eg. 24.5.442.32) address of the server.
The server's IP is listed as the first DNS IP in my only router so all computers inherit it.
If you could detail the config steps that would be great but any info will greatly help! Thanks!

Thank you so much for that guide! It had perfectly clear instructions for something not so simple.
After realizing some of my mistakes along the way of configuring, it was so easy haha.

Similar Messages

Very quick and simple question about a simple sum going wrong.

Ive noticed that im having lots of ocurrences where my maths goes wrong - usually i trace this to ints multiplying doubles and stuff , or its in degrees not radians .
But this one is too simple to seem to cause problems :
screenY = 180 + ( 420 - (( 420 / 2200 ) * xE ) );
heres the code line which does the calculation, and for a particular loop it
ran as xE = 223 .
xE is an int by the way.
For some reason this code always produces screenY = 600 ,
which should only be the case if xE = 0 .
any suggestions as to how i should help the VM get it right?
thanks in advance guys.

Ive noticed that im having lots of ocurrences where
my maths goes wrong - usually i trace this to ints
multiplying doubles and stuff , or its in degrees
not radians .
But this one is too simple to seem to cause problems
screenY = 180 + ( 420 - (( 420 / 2200 ) * xE ) );
heres the code line which does the calculation, and
for a particular loop it
ran as xE = 223 .
xE is an int by the way.
For some reason this code always produces screenY =
600 ,
which should only be the case if xE = 0 .It happens because in integer division 420/2200 is always equal to zero. So, regardless of the value of xE, you're adding 420 + 180, which is 600.
any suggestions as to how i should help the VM get it right? Yes:
double value = 180.0 + (420.0 - ((420.0/ 2200.0)*xE));
screenY = (int)value;You can simplify all this, of course. Why not do that 420/2200 = 0.19090909... calculation once and just substitute the constant value?
%

Quick and simple editing question

Is there any way to zoom out in labview? Like to see more of the block diagram at once?
Thanks.
Intern NSWCCD Carderock.

If you have LabVIEW 7.1, you can show the navigation window (ctrl+shift+N). It lets you see the entire diagram in a small window for navigation.
A better solution is to limit the diagram size. Turn sections into subVIs, clean up the code, etc.
(Have a look at the LabVIEW Style Guide).Message Edited by altenbach on 06-08-2005 08:03 PM
LabVIEW Champion . Do more with less code and in less time .

A quick and simple question about MSI K8N Neo 2 Platinum

I want to overclock my 3500+ but when I go like to 2.4GHZ, the computer isn't stable and sometimes even corrupt some of my Windows files.
My HTT is alright so my mobo stays around 800MHZ
My memory is at 166MHZ so it doesn't go too high
My Vcore is 1.4v but this overclock is so minimal it doesn't cause a problem
Last thing.... AGP and PCI Locks
AGP, no problem, it is locked to 66MHZ, but what about PCI?
I downloaded CoreGen and when I increased the HTT, AGP stood at 66, but PCI increased with it.
Some told me that when you lock AGP to 66, it will also lock PCI, well I have to say that it ain't true 'cause I experienced it myself.
Why isn't PCI Clock not in the motherboard, or is it? and any other motherboard have it???

Never mind, I just noticed I had to put the AGP to 67MHZ to lock both, BUT, I think my comp just sucks in overclocking.....
I set it to 2400MHZ
220x11 with memory at 183MHZ using A64Tweaker so that make my memory set to right on 200MHZ.
My motherboard is set to 880MHZ (800MHZ Origin) so I set HTT to 3 to make 660MHZ and still doesn't work.
When I say it doesn't work it is because my PC doesn't pass Super PI test, it freezes completly after the first LOOP but if I do not run Super PI, the PC won't crash. Is it a Super PI problem or what?

Quick and Dirty Tree Mapping

Hi, i'm trying to do a quick and simple mapping for categories.
Something like...
Vector v = new Vector();
v = PatriotmemDB.getFAQCategories();
FAQCategoryObj catObj = null;
String catname = null;
int catid = 0;
int parent = 0;
int counter = 0;
int prev = 0;
Vector catTree = new Vector();
for(int j=0;j<v.size();j++) {
catObj = (FAQCategoryObj)v.elementAt(j);
parent = catObj.getCatID();
if(parent == counter) {
if(counter == prev) {
catTree.elementAt(counter).add(catObj);
} else {
catTree.elementAt(counter) = new Vector();
catTree.elementAt(counter).add(catObj);
} else {
counter++;
I know this will give an error but basically break out each parent in separate Vectors so that when i loop through them i can test and show in a select list. My table retuns below...
categoryid catname catdesc imglink order parent
1 DRAM DRAM NULL 0 0
2 Solid State Drives Solid State Drives NULL 0 0
3 USB Flash Drives USB Flash Drives NULL 0 0
4 Peripherals Peripherals NULL 0 0
5 Torqx Torqx NULL 0 2
6 Zephyr Zephyr NULL 0 2
7 Xporter XT Boost Xporter XT Boost NULL 0 3
8 Xporter Razzo Xporter Razzo NULL 0 3
Where the parent is the last column.
Thanks for your help

OK, so you have a tree, and you want to product these kind of weird vector slices of the tree, presumably as input to something else.
How is the tree implemented? It looks like a vector of some class, in which the tree structure is implicit in the relationship of some fields of the class, but not an actual tree (composed of nodes, with directed edges between the nodes, no cycles, and a single node is identified as root). Right?
If so, I can imagine one way to do it would be to create a Map<Integer, Vector<TheClass>> Loop through the vector, looking at each class, get the parent reference (which I take to be an integer from your example), and then look up in the map the vector identified for that integer. (If it doesn't exist, create it and add it to the map.) Then add the given class to that vector. When you're done, take the values set from the map.
If you have an actual explicit formal tree, then I'd suggest writing a simple recursive function to span it.
By the way, Vector is kind of long in the tooth. The more canonical List implementations these days are ArrayList or LinkedList.

Resolve.conf, dnsmasq and external DNS servers

I am using dnsmasq to filter out ad urls, so my /etc/resolv.conf looks like that:
# Generated by dhcpcd from wlan0
nameserver 127.0.0.1
domain home
nameserver 192.168.1.254
# /etc/resolv.conf.tail can replace this line
However, it looks like after getting through the url filtration layer of dnsmasq, the URLs are being resolved by a DNS sever of whatever Access Point I am connected to. This create problems, because they often render me unable to connect to services like sourceforge.net, etc.
So, instead of that, I would like my system to fall back to Google and OpenDNS after filtering urls through dnsmasq.
But how can I do that? This is a specific case and wiki does not cover it.
Last edited by Lockheed (2013-05-19 16:50:43)

$ cat /etc/resolv.conf
# Generated by dhcpcd from wlan0
nameserver 127.0.0.1
nameserver 8.8.8.8
domain home
# /etc/resolv.conf.tail can replace this line
The google DNS is what I put in there earlier to be able to use internet after dnsmasq stopped starting.
$ cat /etc/resolvconf.conf
# Configuration for resolvconf(8)
# See resolvconf.conf(5) for details
resolv_conf=/etc/resolv.conf
# If you run a local name server, you should uncomment the below line and
# configure your subscribers configuration files below.
name_servers=127.0.0.1
# Write out dnsmasq extended configuration and resolv files
dnsmasq_conf=/etc/dnsmasq-conf.conf
dnsmasq_resolv=/etc/dnsmasq-resolv.conf
$ cat /etc/dnsmasq.conf
# Configuration file for dnsmasq.
# Format is one option per line, legal options are the same
# as the long options legal on the command line. See
# "/usr/sbin/dnsmasq --help" or "man 8 dnsmasq" for details.
# Listen on this specific port instead of the standard DNS port
# (53). Setting this to zero completely disables DNS function,
# leaving only DHCP and/or TFTP.
#port=5353
# The following two options make you a better netizen, since they
# tell dnsmasq to filter out queries which the public DNS cannot
# answer, and which load the servers (especially the root servers)
# unnecessarily. If you have a dial-on-demand link they also stop
# these requests from bringing up the link unnecessarily.
# Never forward plain names (without a dot or domain part)
#domain-needed
# Never forward addresses in the non-routed address spaces.
#bogus-priv
# Uncomment this to filter useless windows-originated DNS requests
# which can trigger dial-on-demand links needlessly.
# Note that (amongst other things) this blocks all SRV requests,
# so don't use it if you use eg Kerberos, SIP, XMMP or Google-talk.
# This option only affects forwarding, SRV records originating for
# dnsmasq (via srv-host= lines) are not suppressed by it.
#filterwin2k
# Change this line if you want dns to get its upstream servers from
# somewhere other that /etc/resolv.conf
#resolv-file=/etc/resolv-dnsmasq.conf
# By default, dnsmasq will send queries to any of the upstream
# servers it knows about and tries to favour servers to are known
# to be up. Uncommenting this forces dnsmasq to try each query
# with each server strictly in the order they appear in
# /etc/resolv.conf
strict-order
# If you don't want dnsmasq to read /etc/resolv.conf or any other
# file, getting its servers from this file instead (see below), then
# uncomment this.
#no-resolv
# If you don't want dnsmasq to poll /etc/resolv.conf or other resolv
# files for changes and re-read them then uncomment this.
#no-poll
# Add other name servers here, with domain specs if they are for
# non-public domains.
#server=/localnet/192.168.0.1
server=208.67.222.222
server=208.67.220.220
# Example of routing PTR queries to nameservers: this will send all
# address->name queries for 192.168.3/24 to nameserver 10.1.2.3
#server=/3.168.192.in-addr.arpa/10.1.2.3
# Add local-only domains here, queries in these domains are answered
# from /etc/hosts or DHCP only.
#local=/localnet/
# Add domains which you want to force to an IP address here.
# The example below send any host in double-click.net to a local
# web-server.
#address=/double-click.net/127.0.0.1
# --address (and --server) work with IPv6 addresses too.
#address=/www.thekelleys.org.uk/fe80::20d:60ff:fe36:f83
# You can control how dnsmasq talks to a server: this forces
# queries to 10.1.2.3 to be routed via eth1
# server=10.1.2.3@eth1
# and this sets the source (ie local) address used to talk to
# 10.1.2.3 to 192.168.1.1 port 55 (there must be a interface with that
# IP on the machine, obviously).
# [email protected]#55
# If you want dnsmasq to change uid and gid to something other
# than the default, edit the following lines.
#user=
#group=
# If you want dnsmasq to listen for DHCP and DNS requests only on
# specified interfaces (and the loopback) give the name of the
# interface (eg eth0) here.
# Repeat the line for more than one interface.
#interface=lo
# Or you can specify which interface _not_ to listen on
#except-interface=
# Or which to listen on by address (remember to include 127.0.0.1 if
# you use this.)
#listen-address=127.0.0.1
# If you want dnsmasq to provide only DNS service on an interface,
# configure it as shown above, and then use the following line to
# disable DHCP and TFTP on it.
#no-dhcp-interface=
# On systems which support it, dnsmasq binds the wildcard address,
# even when it is listening on only some interfaces. It then discards
# requests that it shouldn't reply to. This has the advantage of
# working even when interfaces come and go and change address. If you
# want dnsmasq to really bind only the interfaces it is listening on,
# uncomment this option. About the only time you may need this is when
# running another nameserver on the same machine.
#bind-interfaces
# If you don't want dnsmasq to read /etc/hosts, uncomment the
# following line.
#no-hosts
# or if you want it to read another file, as well as /etc/hosts, use
# this.
addn-hosts=/etc/hosts.block
#hostsfile=/etc/hosts.block
# Set this (and domain: see below) if you want to have a domain
# automatically added to simple names in a hosts-file.
#expand-hosts
# Set the domain for dnsmasq. this is optional, but if it is set, it
# does the following things.
# 1) Allows DHCP hosts to have fully qualified domain names, as long
# as the domain part matches this setting.
# 2) Sets the "domain" DHCP option thereby potentially setting the
# domain of all systems configured by DHCP
# 3) Provides the domain part for "expand-hosts"
#domain=thekelleys.org.uk
# Set a different domain for a particular subnet
#domain=wireless.thekelleys.org.uk,192.168.2.0/24
# Same idea, but range rather then subnet
#domain=reserved.thekelleys.org.uk,192.68.3.100,192.168.3.200
# Uncomment this to enable the integrated DHCP server, you need
# to supply the range of addresses available for lease and optionally
# a lease time. If you have more than one network, you will need to
# repeat this for each network on which you want to supply DHCP
# service.
#dhcp-range=192.168.0.50,192.168.0.150,12h
# This is an example of a DHCP range where the netmask is given. This
# is needed for networks we reach the dnsmasq DHCP server via a relay
# agent. If you don't know what a DHCP relay agent is, you probably
# don't need to worry about this.
#dhcp-range=192.168.0.50,192.168.0.150,255.255.255.0,12h
# This is an example of a DHCP range which sets a tag, so that
# some DHCP options may be set only for this network.
#dhcp-range=set:red,192.168.0.50,192.168.0.150
# Use this DHCP range only when the tag "green" is set.
#dhcp-range=tag:green,192.168.0.50,192.168.0.150,12h
# Specify a subnet which can't be used for dynamic address allocation,
# is available for hosts with matching --dhcp-host lines. Note that
# dhcp-host declarations will be ignored unless there is a dhcp-range
# of some type for the subnet in question.
# In this case the netmask is implied (it comes from the network
# configuration on the machine running dnsmasq) it is possible to give
# an explicit netmask instead.
#dhcp-range=192.168.0.0,static
# Enable DHCPv6. Note that the prefix-length does not need to be specified
# and defaults to 64 if missing/
#dhcp-range=1234::2, 1234::500, 64, 12h
# Do Router Advertisements, BUT NOT DHCP for this subnet.
#dhcp-range=1234::, ra-only
# Do Router Advertisements, BUT NOT DHCP for this subnet, also try and
# add names to the DNS for the IPv6 address of SLAAC-configured dual-stack
# hosts. Use the DHCPv4 lease to derive the name, network segment and
# MAC address and assume that the host will also have an
# IPv6 address calculated using the SLAAC alogrithm.
#dhcp-range=1234::, ra-names
# Do Router Advertisements, BUT NOT DHCP for this subnet.
# Set the lifetime to 46 hours. (Note: minimum lifetime is 2 hours.)
#dhcp-range=1234::, ra-only, 48h
# Do DHCP and Router Advertisements for this subnet. Set the A bit in the RA
# so that clients can use SLAAC addresses as well as DHCP ones.
#dhcp-range=1234::2, 1234::500, slaac
# Do Router Advertisements and stateless DHCP for this subnet. Clients will
# not get addresses from DHCP, but they will get other configuration information.
# They will use SLAAC for addresses.
#dhcp-range=1234::, ra-stateless
# Do stateless DHCP, SLAAC, and generate DNS names for SLAAC addresses
# from DHCPv4 leases.
#dhcp-range=1234::, ra-stateless, ra-names
# Do router advertisements for all subnets where we're doing DHCPv6
# Unless overriden by ra-stateless, ra-names, et al, the router
# advertisements will have the M and O bits set, so that the clients
# get addresses and configuration from DHCPv6, and the A bit reset, so the
# clients don't use SLAAC addresses.
#enable-ra
# Supply parameters for specified hosts using DHCP. There are lots
# of valid alternatives, so we will give examples of each. Note that
# IP addresses DO NOT have to be in the range given above, they just
# need to be on the same network. The order of the parameters in these
# do not matter, it's permissible to give name, address and MAC in any
# order.
# Always allocate the host with Ethernet address 11:22:33:44:55:66
# The IP address 192.168.0.60
#dhcp-host=11:22:33:44:55:66,192.168.0.60
# Always set the name of the host with hardware address
# 11:22:33:44:55:66 to be "fred"
#dhcp-host=11:22:33:44:55:66,fred
# Always give the host with Ethernet address 11:22:33:44:55:66
# the name fred and IP address 192.168.0.60 and lease time 45 minutes
#dhcp-host=11:22:33:44:55:66,fred,192.168.0.60,45m
# Give a host with Ethernet address 11:22:33:44:55:66 or
# 12:34:56:78:90:12 the IP address 192.168.0.60. Dnsmasq will assume
# that these two Ethernet interfaces will never be in use at the same
# time, and give the IP address to the second, even if it is already
# in use by the first. Useful for laptops with wired and wireless
# addresses.
#dhcp-host=11:22:33:44:55:66,12:34:56:78:90:12,192.168.0.60
# Give the machine which says its name is "bert" IP address
# 192.168.0.70 and an infinite lease
#dhcp-host=bert,192.168.0.70,infinite
# Always give the host with client identifier 01:02:02:04
# the IP address 192.168.0.60
#dhcp-host=id:01:02:02:04,192.168.0.60
# Always give the host with client identifier "marjorie"
# the IP address 192.168.0.60
#dhcp-host=id:marjorie,192.168.0.60
# Enable the address given for "judge" in /etc/hosts
# to be given to a machine presenting the name "judge" when
# it asks for a DHCP lease.
#dhcp-host=judge
# Never offer DHCP service to a machine whose Ethernet
# address is 11:22:33:44:55:66
#dhcp-host=11:22:33:44:55:66,ignore
# Ignore any client-id presented by the machine with Ethernet
# address 11:22:33:44:55:66. This is useful to prevent a machine
# being treated differently when running under different OS's or
# between PXE boot and OS boot.
#dhcp-host=11:22:33:44:55:66,id:*
# Send extra options which are tagged as "red" to
# the machine with Ethernet address 11:22:33:44:55:66
#dhcp-host=11:22:33:44:55:66,set:red
# Send extra options which are tagged as "red" to
# any machine with Ethernet address starting 11:22:33:
#dhcp-host=11:22:33:*:*:*,set:red
# Give a fixed IPv6 address and name to client with
# DUID 00:01:00:01:16:d2:83:fc:92:d4:19:e2:d8:b2
# Note the MAC addresses CANNOT be used to identify DHCPv6 clients.
# Note also the they [] around the IPv6 address are obilgatory.
#dhcp-host=id:00:01:00:01:16:d2:83:fc:92:d4:19:e2:d8:b2, fred, [1234::5]
# Ignore any clients which are not specified in dhcp-host lines
# or /etc/ethers. Equivalent to ISC "deny unknown-clients".
# This relies on the special "known" tag which is set when
# a host is matched.
#dhcp-ignore=tag:!known
# Send extra options which are tagged as "red" to any machine whose
# DHCP vendorclass string includes the substring "Linux"
#dhcp-vendorclass=set:red,Linux
# Send extra options which are tagged as "red" to any machine one
# of whose DHCP userclass strings includes the substring "accounts"
#dhcp-userclass=set:red,accounts
# Send extra options which are tagged as "red" to any machine whose
# MAC address matches the pattern.
#dhcp-mac=set:red,00:60:8C:*:*:*
# If this line is uncommented, dnsmasq will read /etc/ethers and act
# on the ethernet-address/IP pairs found there just as if they had
# been given as --dhcp-host options. Useful if you keep
# MAC-address/host mappings there for other purposes.
#read-ethers
# Send options to hosts which ask for a DHCP lease.
# See RFC 2132 for details of available options.
# Common options can be given to dnsmasq by name:
# run "dnsmasq --help dhcp" to get a list.
# Note that all the common settings, such as netmask and
# broadcast address, DNS server and default route, are given
# sane defaults by dnsmasq. You very likely will not need
# any dhcp-options. If you use Windows clients and Samba, there
# are some options which are recommended, they are detailed at the
# end of this section.
# Override the default route supplied by dnsmasq, which assumes the
# router is the same machine as the one running dnsmasq.
#dhcp-option=3,1.2.3.4
# Do the same thing, but using the option name
#dhcp-option=option:router,1.2.3.4
# Override the default route supplied by dnsmasq and send no default
# route at all. Note that this only works for the options sent by
# default (1, 3, 6, 12, 28) the same line will send a zero-length option
# for all other option numbers.
#dhcp-option=3
# Set the NTP time server addresses to 192.168.0.4 and 10.10.0.5
#dhcp-option=option:ntp-server,192.168.0.4,10.10.0.5
# Send DHCPv6 option. Note [] around IPv6 addresses.
#dhcp-option=option6:dns-server,[1234::77],[1234::88]
# Send DHCPv6 option for namservers as the machine running
# dnsmasq and another.
#dhcp-option=option6:dns-server,[::],[1234::88]
# Ask client to poll for option changes every six hours. (RFC4242)
#dhcp-option=option6:information-refresh-time,6h
# Set the NTP time server address to be the same machine as
# is running dnsmasq
#dhcp-option=42,0.0.0.0
# Set the NIS domain name to "welly"
#dhcp-option=40,welly
# Set the default time-to-live to 50
#dhcp-option=23,50
# Set the "all subnets are local" flag
#dhcp-option=27,1
# Send the etherboot magic flag and then etherboot options (a string).
#dhcp-option=128,e4:45:74:68:00:00
#dhcp-option=129,NIC=eepro100
# Specify an option which will only be sent to the "red" network
# (see dhcp-range for the declaration of the "red" network)
# Note that the tag: part must precede the option: part.
#dhcp-option = tag:red, option:ntp-server, 192.168.1.1
# The following DHCP options set up dnsmasq in the same way as is specified
# for the ISC dhcpcd in
# http://www.samba.org/samba/ftp/docs/textdocs/DHCP-Server-Configuration.txt
# adapted for a typical dnsmasq installation where the host running
# dnsmasq is also the host running samba.
# you may want to uncomment some or all of them if you use
# Windows clients and Samba.
#dhcp-option=19,0 # option ip-forwarding off
#dhcp-option=44,0.0.0.0 # set netbios-over-TCP/IP nameserver(s) aka WINS server(s)
#dhcp-option=45,0.0.0.0 # netbios datagram distribution server
#dhcp-option=46,8 # netbios node type
# Send an empty WPAD option. This may be REQUIRED to get windows 7 to behave.
#dhcp-option=252,"\n"
# Send RFC-3397 DNS domain search DHCP option. WARNING: Your DHCP client
# probably doesn't support this......
#dhcp-option=option:domain-search,eng.apple.com,marketing.apple.com
# Send RFC-3442 classless static routes (note the netmask encoding)
#dhcp-option=121,192.168.1.0/24,1.2.3.4,10.0.0.0/8,5.6.7.8
# Send vendor-class specific options encapsulated in DHCP option 43.
# The meaning of the options is defined by the vendor-class so
# options are sent only when the client supplied vendor class
# matches the class given here. (A substring match is OK, so "MSFT"
# matches "MSFT" and "MSFT 5.0"). This example sets the
# mtftp address to 0.0.0.0 for PXEClients.
#dhcp-option=vendor:PXEClient,1,0.0.0.0
# Send microsoft-specific option to tell windows to release the DHCP lease
# when it shuts down. Note the "i" flag, to tell dnsmasq to send the
# value as a four-byte integer - that's what microsoft wants. See
# http://technet2.microsoft.com/WindowsServer/en/library/a70f1bb7-d2d4-49f0-96d6-4b7414ecfaae1033.mspx?mfr=true
#dhcp-option=vendor:MSFT,2,1i
# Send the Encapsulated-vendor-class ID needed by some configurations of
# Etherboot to allow is to recognise the DHCP server.
#dhcp-option=vendor:Etherboot,60,"Etherboot"
# Send options to PXELinux. Note that we need to send the options even
# though they don't appear in the parameter request list, so we need
# to use dhcp-option-force here.
# See http://syslinux.zytor.com/pxe.php#special for details.
# Magic number - needed before anything else is recognised
#dhcp-option-force=208,f1:00:74:7e
# Configuration file name
#dhcp-option-force=209,configs/common
# Path prefix
#dhcp-option-force=210,/tftpboot/pxelinux/files/
# Reboot time. (Note 'i' to send 32-bit value)
#dhcp-option-force=211,30i
# Set the boot filename for netboot/PXE. You will only need
# this is you want to boot machines over the network and you will need
# a TFTP server; either dnsmasq's built in TFTP server or an
# external one. (See below for how to enable the TFTP server.)
#dhcp-boot=pxelinux.0
# The same as above, but use custom tftp-server instead machine running dnsmasq
#dhcp-boot=pxelinux,server.name,192.168.1.100
# Boot for Etherboot gPXE. The idea is to send two different
# filenames, the first loads gPXE, and the second tells gPXE what to
# load. The dhcp-match sets the gpxe tag for requests from gPXE.
#dhcp-match=set:gpxe,175 # gPXE sends a 175 option.
#dhcp-boot=tag:!gpxe,undionly.kpxe
#dhcp-boot=mybootimage
# Encapsulated options for Etherboot gPXE. All the options are
# encapsulated within option 175
#dhcp-option=encap:175, 1, 5b # priority code
#dhcp-option=encap:175, 176, 1b # no-proxydhcp
#dhcp-option=encap:175, 177, string # bus-id
#dhcp-option=encap:175, 189, 1b # BIOS drive code
#dhcp-option=encap:175, 190, user # iSCSI username
#dhcp-option=encap:175, 191, pass # iSCSI password
# Test for the architecture of a netboot client. PXE clients are
# supposed to send their architecture as option 93. (See RFC 4578)
#dhcp-match=peecees, option:client-arch, 0 #x86-32
#dhcp-match=itanics, option:client-arch, 2 #IA64
#dhcp-match=hammers, option:client-arch, 6 #x86-64
#dhcp-match=mactels, option:client-arch, 7 #EFI x86-64
# Do real PXE, rather than just booting a single file, this is an
# alternative to dhcp-boot.
#pxe-prompt="What system shall I netboot?"
# or with timeout before first available action is taken:
#pxe-prompt="Press F8 for menu.", 60
# Available boot services. for PXE.
#pxe-service=x86PC, "Boot from local disk"
# Loads <tftp-root>/pxelinux.0 from dnsmasq TFTP server.
#pxe-service=x86PC, "Install Linux", pxelinux
# Loads <tftp-root>/pxelinux.0 from TFTP server at 1.2.3.4.
# Beware this fails on old PXE ROMS.
#pxe-service=x86PC, "Install Linux", pxelinux, 1.2.3.4
# Use bootserver on network, found my multicast or broadcast.
#pxe-service=x86PC, "Install windows from RIS server", 1
# Use bootserver at a known IP address.
#pxe-service=x86PC, "Install windows from RIS server", 1, 1.2.3.4
# If you have multicast-FTP available,
# information for that can be passed in a similar way using options 1
# to 5. See page 19 of
# http://download.intel.com/design/archives/wfm/downloads/pxespec.pdf
# Enable dnsmasq's built-in TFTP server
#enable-tftp
# Set the root directory for files available via FTP.
#tftp-root=/var/ftpd
# Make the TFTP server more secure: with this set, only files owned by
# the user dnsmasq is running as will be send over the net.
#tftp-secure
# This option stops dnsmasq from negotiating a larger blocksize for TFTP
# transfers. It will slow things down, but may rescue some broken TFTP
# clients.
#tftp-no-blocksize
# Set the boot file name only when the "red" tag is set.
#dhcp-boot=net:red,pxelinux.red-net
# An example of dhcp-boot with an external TFTP server: the name and IP
# address of the server are given after the filename.
# Can fail with old PXE ROMS. Overridden by --pxe-service.
#dhcp-boot=/var/ftpd/pxelinux.0,boothost,192.168.0.3
# If there are multiple external tftp servers having a same name
# (using /etc/hosts) then that name can be specified as the
# tftp_servername (the third option to dhcp-boot) and in that
# case dnsmasq resolves this name and returns the resultant IP
# addresses in round robin fasion. This facility can be used to
# load balance the tftp load among a set of servers.
#dhcp-boot=/var/ftpd/pxelinux.0,boothost,tftp_server_name
# Set the limit on DHCP leases, the default is 150
#dhcp-lease-max=150
# The DHCP server needs somewhere on disk to keep its lease database.
# This defaults to a sane location, but if you want to change it, use
# the line below.
#dhcp-leasefile=/var/lib/misc/dnsmasq.leases
# Set the DHCP server to authoritative mode. In this mode it will barge in
# and take over the lease for any client which broadcasts on the network,
# whether it has a record of the lease or not. This avoids long timeouts
# when a machine wakes up on a new network. DO NOT enable this if there's
# the slightest chance that you might end up accidentally configuring a DHCP
# server for your campus/company accidentally. The ISC server uses
# the same option, and this URL provides more information:
# http://www.isc.org/files/auth.html
#dhcp-authoritative
# Run an executable when a DHCP lease is created or destroyed.
# The arguments sent to the script are "add" or "del",
# then the MAC address, the IP address and finally the hostname
# if there is one.
#dhcp-script=/bin/echo
# Set the cachesize here.
#cache-size=150
# If you want to disable negative caching, uncomment this.
#no-negcache
# Normally responses which come from /etc/hosts and the DHCP lease
# file have Time-To-Live set as zero, which conventionally means
# do not cache further. If you are happy to trade lower load on the
# server for potentially stale date, you can set a time-to-live (in
# seconds) here.
#local-ttl=
# If you want dnsmasq to detect attempts by Verisign to send queries
# to unregistered .com and .net hosts to its sitefinder service and
# have dnsmasq instead return the correct NXDOMAIN response, uncomment
# this line. You can add similar lines to do the same for other
# registries which have implemented wildcard A records.
#bogus-nxdomain=64.94.110.11
# If you want to fix up DNS results from upstream servers, use the
# alias option. This only works for IPv4.
# This alias makes a result of 1.2.3.4 appear as 5.6.7.8
#alias=1.2.3.4,5.6.7.8
# and this maps 1.2.3.x to 5.6.7.x
#alias=1.2.3.0,5.6.7.0,255.255.255.0
# and this maps 192.168.0.10->192.168.0.40 to 10.0.0.10->10.0.0.40
#alias=192.168.0.10-192.168.0.40,10.0.0.0,255.255.255.0
# Change these lines if you want dnsmasq to serve MX records.
# Return an MX record named "maildomain.com" with target
# servermachine.com and preference 50
#mx-host=maildomain.com,servermachine.com,50
# Set the default target for MX records created using the localmx option.
#mx-target=servermachine.com
# Return an MX record pointing to the mx-target for all local
# machines.
#localmx
# Return an MX record pointing to itself for all local machines.
#selfmx
# Change the following lines if you want dnsmasq to serve SRV
# records. These are useful if you want to serve ldap requests for
# Active Directory and other windows-originated DNS requests.
# See RFC 2782.
# You may add multiple srv-host lines.
# The fields are <name>,<target>,<port>,<priority>,<weight>
# If the domain part if missing from the name (so that is just has the
# service and protocol sections) then the domain given by the domain=
# config option is used. (Note that expand-hosts does not need to be
# set for this to work.)
# A SRV record sending LDAP for the example.com domain to
# ldapserver.example.com port 389
#srv-host=_ldap._tcp.example.com,ldapserver.example.com,389
# A SRV record sending LDAP for the example.com domain to
# ldapserver.example.com port 389 (using domain=)
#domain=example.com
#srv-host=_ldap._tcp,ldapserver.example.com,389
# Two SRV records for LDAP, each with different priorities
#srv-host=_ldap._tcp.example.com,ldapserver.example.com,389,1
#srv-host=_ldap._tcp.example.com,ldapserver.example.com,389,2
# A SRV record indicating that there is no LDAP server for the domain
# example.com
#srv-host=_ldap._tcp.example.com
# The following line shows how to make dnsmasq serve an arbitrary PTR
# record. This is useful for DNS-SD. (Note that the
# domain-name expansion done for SRV records _does_not
# occur for PTR records.)
#ptr-record=_http._tcp.dns-sd-services,"New Employee Page._http._tcp.dns-sd-services"
# Change the following lines to enable dnsmasq to serve TXT records.
# These are used for things like SPF and zeroconf. (Note that the
# domain-name expansion done for SRV records _does_not
# occur for TXT records.)
#Example SPF.
#txt-record=example.com,"v=spf1 a -all"
#Example zeroconf
#txt-record=_http._tcp.example.com,name=value,paper=A4
# Provide an alias for a "local" DNS name. Note that this _only_ works
# for targets which are names from DHCP or /etc/hosts. Give host
# "bert" another name, bertrand
#cname=bertand,bert
# For debugging purposes, log each DNS query as it passes through
# dnsmasq.
#log-queries
# Log lots of extra information about DHCP transactions.
#log-dhcp
# Include a another lot of configuration options.
#conf-file=/etc/dnsmasq-resolvconf.conf
#conf-dir=/etc/dnsmasq.d
domain-needed
interface=lo
# If dnsmasq is compiled for DBus then we can take
# advantage of not having to restart dnsmasq.
enable-dbus
conf-file=/etc/dnsmasq-conf.conf
resolv-file=/etc/dnsmasq-resolv.conf
Logs:
May 23 00:01:06 panzor systemd[1]: Failed to start A lightweight DHCP and caching DNS server.
May 23 00:01:10 panzor dhcpcd[27267]: dhcpcd not running
May 23 00:01:10 panzor kernel: [ 7771.282756] iwl4965 0000:03:00.0: Can't stop Rx DMA.
May 23 00:01:10 panzor dhcpcd[27294]: dhcpcd not running
May 23 00:01:11 panzor dhcpcd[27330]: dhcpcd not running
May 23 00:01:14 panzor dhcpcd[27373]: wlan0: sendmsg: Cannot assign requested address
May 23 00:01:18 panzor dhcpcd[27373]: wlan0: sendmsg: Operation not permitted
May 23 00:01:22 panzor dhcpcd[27395]: wlan0: sendmsg: Operation not permitted
May 23 00:01:26 panzor dhcpcd[27395]: wlan0: sendmsg: Operation not permitted
For domain filtration, if I remember correctly, I am using this
https://bbs.archlinux.org/viewtopic.php?id=139784

Sender and Receiver IDOC config Settings

Guys I have just come up with this document as a quick reference guide to enable me to be able to configure IDOC scenarios quickly and efficiently. Couls you please let me know if this looks ok and all is in the correct order.
Quick Guide to Scenarios
Note A Ports only purpose is to allow either the SAP R/3 Backend system to establish an RFC connection with XI or allow the XI to establish an RFC Connection with the Receiver SAP R/3 system.
Note An RFC Destinations purpose is to: A) Communicate with the SAP system
B) Pull metadata from either the Sender/Receiver SAP R/3 System or another reference system that contains the same IDOC.
Sender IDOC Scenario
When configuring an IDOC Sender adapter there are a few things that you need to configure before you even start with the Config Directory itself.
Because IDOC Adapter resides on the ABAP stack no sender agreement or sender Comm Channel is necessary
Your main configuration is in R/3. You configure R/3 to send the IDOC to XI so hence you dont need an IDOC Adapter or Comm Channel.
1. You need to define an RFC destination to XI in the R/3 Backend system. (SM59). This RFC destination is used to retrieve the IDOC metadata from the sender system. The IDOC adapter needs these metadata to create the corresponding IDOC-XML message from the RFC stream.
2. Assign the destination to a Port in the R/3 Backend system (WE21)
3. Define your Partner Profiles for the IDOC you are trying to send and Reference that Port there as well (WE20)
Based on the above conditions, you do not need a Sender Comm Channel for IDOC or a Sender Agreement for the business scenario. Your only configuration in the Config Directory is to define R/3 as a Business System (no Comm Channel) and define the Receiver Business System along with the Receiver Determination, Interface Determination and Receiver agreement.
I'm not sure if this step is necessary in the sender IDOC scenario -
In XI box you must also define the ports in IDX1 which allows you to establish an RFC connection to pull the metadata in from the backend system, by specifying the RFC destination from where you want to get the info from. This system is defined by the sender port and the client in the IDOC control record. It is either the sender SAP system or an SAP reference system.
There are certain cases which you also need to use IDX2 (Cache). XI itself does need the IDOC metadata to execute the interface but it can usually use IDX1 to pull this data either from the SAP R/3 system or an equivalent reference system. However if there is already cached metadata and the IDOC has changed then IDX1 will not execute. In this instance you can pull this metadata manually using IDX2 (XI Box).
Receiver IDOC
When you receive an IDOC things are a little more complex. You do need a Sender agreement and Comm Channel defined. Again there is much to be done in XI and the R/3 Receiver system before you get to the configuration of the Config Directory.
1. In XI you must configure the RFC destination which enables XI to communicate with the Target System (SM59)
2. In XI you must then create the port which allows you to establish an RFC Connection. In this port you define the RFC destination you previously defined. (IDX1)
3. You then must also ensure that a Partner Profile has been established in the Target system which allows XI to send IDOCs to the Target system. (WE20)
Once the above is completed you can then continue to configure your IDOC scenario in the Config directory. In your Receiver Adapter you reference both the Port and RFC destination that you just established along with the Release which is to be the Target systems release. You must also specify an Interface version which again is the Target systems version.
There are certain cases which you also need to use IDX2 (Cache). XI itself does need the IDOC metadata to execute the interface but it can usually use IDX1 to pull this data either from the SAP R/3 system or an equivalent reference system. However if there is already cached metadata and the IDOC has changed then IDX1 will not execute. In this instance you can pull this metadata manually using IDX2 (XI Box).
Apart from the above the rest of the steps in the Config Directory are as normal.
Message was edited by:
 Alex Ong

Hi,
As per my knowledge you need to configure port in IDXI in XI to pull the metadata.
Its a mandatory step to pull the metadata whatever be scenario like whether you are sending an IDoc or receiving an IDoc.
So please configure RFC destination, IDX1 and IDX2 in XI side.
Only after pulling the IDoc metadata you can proceed with any of the IDoc scenario.
Whenever there a IDoc is changed you need to delete the previous metadata and pull it again. In such situations you can use the already existing port in IDX1.
Hope this helps you out.
Thanks and Regards,
Vineetha

OS X 10.4.11 Server - configured name and reverse DNS do not match / DNS

Hi all,
I have looked for similar posts but all seem to have different scenarios, hoping to get an answer from someone more experienced than myself before I do anything silly.
Help much appreciated!
Scenario:
We run a 10.4.11 OS X Server on an XServe, hosted at an ISP. ISP provides all DNS services, incl. the reversed DNS entry.
I am currently only running the following services (based on the display in ServerAdmin):
AFP
Firewall
iChat
Mail
QuickTimeStreaming
Web
All others (incl. DNS) are grayed out. (As ISP instructed us not to add a DNS service on our box, that's "normal" according to my experiences with dedicated /co-location server hosting).
We never used changeip after the initial setup, meaning the server's
Current Hostname = somename.local and
DNS Hostname = mail.ourdomainname.net
So in system.log I find this re-occuring entry:
Jul 8 11:41:22 somename servermgrd: servermgr_dns: configured name and reverse DNS name do not match (somename.local != mail.ourdomainname.net), various services may not function properly - use changeip to repair and/or correct DNS
Finally, my question:
As Mail and Web services etc. are currently running OK from what I can tell,
1) do I HAVE to change this at all?
2) Would it be much better / why?
3) Could I change this using the following command
(111.11.111.1 indicating the server's IP address)
changeip 111.11.111.1 111.11.111.1 somename.local mail.ourdomainname.net
4) without running a DNS server on the machine, i.e. DNS service is not required for this to work?
5) obviously I want to be able to use Server Admin after I issue this command...
6) can I fall back easily in case this would screw it up, or is there no risk whatsoever doing this in my case?
THANK YOU so much for any help!

Hi Jonas
If port 443 is already being used on the same box as KMS then it will complain and probably not start the service? I've seen this with LDAP port 636. This is when Kerio is installed on a server configured as an OD Master. Clearly the port can't be used by both servers.
It might be easier to change the port your sites are currently using to something else? Although don't do anything yet. Pose the question to Kerio Support and see what advice they offer.
Yes moving the mail to a local folder on the mail client will do it.
Is Kerio going on the same box? If its a different box (presumably different IP address?) Then what you can do is to port forward to the new server's IP address instead of disabling it. This way while you are bringing the new server on line users can still send mail right up until the time you give instructions on changing their inbound/outbound mail server details. Of course they won't be able to receive but if you time it right they may not even get an error message? Depends on what their schedules are.
If it was me I would choose IMAP every time. As the mail admin you have full control and a central location for easy backup. KMS has a built in archiving feature that makes this a simple process. This is an easier option than going round individual client machines and making sure mail held locally in POP accounts are backed up. Besides there is always someone who falls through the loop and I'm not taking into account drive failures. It makes good sense anyway as there is talk of legislation being introduced to make this a requirement for businesses who run their own mail servers. This is certainly true for certain parts of the US and what usually happens there is generally taken up in the UK and most parts of Europe.
Kerio's WebMail Client means users don't even have to have their own computer. Just as long as they have access to one that has access to the internet they can send/receive mail. No need for dedicated mail applications such as Apple Mail, Thunderbird, Entourage etc. How mail is uses remains consistent for all users.
Yes. I did this not so long ago with Leopard's built in Mail Server. I sent an e-mail defining a time when no inbound mail would be received. Disabled port forwarding for SMTP port 25 and approx 30 minutes after that another mail stating no outbound mail should be sent. Once everything was swopped over (we were changing from a G4 10.4 server to a G5 10.5 Server) port 25 was enabled, new server brought online and everyone was mailing again with no appreciable downtime.
These boxes were to have the same IP address hence the slightly different approach.
Does this help?
Tony

Simple xml config file

I have created a simple config file using something like:
 XMLEncoder e = new XMLEncoder(
 new BufferedOutputStream(
 new FileOutputStream("Config.xml")));
 e.writeObject(base.toString());
 e.writeObject(numberFrom);
 e.writeObject(numberTo);
 e.writeObject(numberPad);
 e.writeObject(maxTasks);
 e.writeObject(maxSubTasks);
 e.writeObject(textFrom);
 e.writeObject(textTo);
 e.close();which produces a file like:
<?xml version="1.0" encoding="UTF-8"?>
<java version="1.4.2_05" class="java.beans.XMLDecoder">
<string>C:\</string>
<int>1</int>
<int>20</int>
<int>2</int>
<int>0</int>
<int>1</int>
<string>a</string>
<string>z</string>
</java> I want to make it a bit more version proof so need to get something more like:
<?xml version="1.0" encoding="UTF-8"?>
<program name=myprog>
<dir>C:\</dir>
<version>1</version>
<myval1>20</myval1>
<myval2>2</myval2>
</program>There's probably loads of errors in that bit;) but you get the idea. I'm a bit new to xml programming.
Can anyone give me any urls of help or examples that might do this?
Thanks,
David.

You could use a binding api such as JAXB or xmlbeans. In essence these apis abstract the xml as pure java objects. Alternatively you could use an xml parser such as dom4j and build the XML 'by hand'. This class will create an example config file and write it to the file system
import java.io.BufferedWriter;
import java.io.File;
import java.io.FileWriter;
import java.io.IOException;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.parsers.ParserConfigurationException;
import org.apache.xml.serialize.OutputFormat;
import org.apache.xml.serialize.XMLSerializer;
import org.w3c.dom.Document;
import org.w3c.dom.Element;
import org.w3c.dom.Text;
* Class to create a simple xml config file using W3C api
* @author wollnyj
public class CreateConfig {
 * create the config file
 *?xml version="1.0" encoding="UTF-8"?>
 *<program name=myprog>
 * <dir>C:\</dir>
 * <version>1</version>
 * <myval1>20</myval1>
 * <myval2>2</myval2>
 *</program>
 * @param configFile
 * @throws ParserConfigurationException
 * @throws IOException
 public CreateConfig(String configFile) throws ParserConfigurationException, IOException {
 //Document doc = parseXml(configFile);
 DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
 Document doc = factory.newDocumentBuilder().newDocument();
 Element program = doc.createElement("program");
 program.setAttribute("name","myprog");
 Element dir = createEle("dir","c:\\",doc);
 Element version = createEle("version","1",doc);
 Element val1 = createEle("myval1","20",doc);
 // etc...
 program.appendChild(dir);
 program.appendChild(version);
 program.appendChild(val1);
 doc.appendChild(program);
 write(doc,new File(configFile));
 * @param args
 * @throws Exception
 public static void main(String[]args) throws Exception {
 CreateConfig create = new CreateConfig("F:\\config.xml");
 * Write an xml document to the file system
 * @param document The document to be written
 * @param xmlFile The output file
 * @throws IOException The file does not exist or could not be created
 private void write(Document document, File xmlFile) throws IOException {
 OutputFormat format = new OutputFormat(document);
 format.setIndent(4);
 format.setLineSeparator(System.getProperty("line.separator"));
 format.setLineWidth(80);
 FileWriter writer = new FileWriter(xmlFile);
 XMLSerializer fileSerial = new XMLSerializer(new BufferedWriter(writer), format);
 fileSerial.asDOMSerializer();
 fileSerial.serialize(document);
 private Element createEle(String name, String value, Document doc) {
 Element ele = doc.createElement(name);
 Text textNode = doc.createTextNode(value);
 ele.appendChild(textNode);
 return ele;
}

Simple DNS split example

Hello,
I'm using a Cisco 1841 over DSL for internet access and a personal web server. I have searched for a simple DNS split configuration onet the Internet, but none of the examples I have found had worked on my router.
Does anyone have a simple example of DNS split to share with me? I'm newbie on Cisco routers.
Regards,
Marcio

Hello Peter!
I'm not using the Split DNS on my router yet! Let me explain what's happening.
I have a web server running on my private network on the machine 10.10.10.11 and I can access it using the mentioned address. This server have a FDQN and I can reach it from outside my network (Internet) without any issue.
I would like to use the FDQN to access it from machines inside my private network, but I cannot due to some security feature on cisco router. I have read some articles stating we need to have a "Split DNS" to allow machines inside the private network can access the web server on the address 10.10.10.11 using the FDQN, as machines outside the private network do.
I tryed to find a simple "Split DNS" to try here, but I didn't found any that could be used. All I have found are very complex examples. I'm using the following firmaware on the router:
HomeNet#sh version
Cisco IOS Software, 1841 Software (C1841-IPBASEK9-M), Version 12.4(24)T3, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2010 by Cisco Systems, Inc.
Compiled Tue 23-Mar-10 05:11 by prod_rel_team
ROM: System Bootstrap, Version 12.4(13r)T5, RELEASE SOFTWARE (fc1)
HomeNet uptime is 23 hours, 37 minutes
System returned to ROM by power-on
System image file is "flash:c1841-ipbasek9-mz.124-24.T3.bin"
I'm not using Cisco Router as a DHCP server, since I have a Linux machine running ISC-DHCP-SERVER on my network. I have attached some pictures to ilustrate the issue, one accessing using FDQN and other using server IP address.
Best Regards!
Marcio

Lesson for this weekend: Don't trust "quick and easy"

When they say a process will be simple, quick and easy it really means it may or may not explode in your face!Started out on Friday simply wanting to write a new post for my site and update some old articles. Found out the php upload limit was too low for some of the server photos I wanted to add. No problem, just increase the limit right? Well no. Since the site was still in "Safe Mode" I couldn't change any of the advanced functions. The solution? Switch to Free Mode, billed as a simple process of a few clicks. Lets do this then! Clicked the deceptively easy "Switch to Free Mode" button prepared for a few clicks and getting on with my day. Filled out the information, set the flags I wanted, clicked go.....and it failed. That's fine, it went back to safe mode so I can just retry, right? Fails again. Third times the charm? Nope.At this...
This topic first appeared in the Spiceworks Community

When they say a process will be simple, quick and easy it really means it may or may not explode in your face!Started out on Friday simply wanting to write a new post for my site and update some old articles. Found out the php upload limit was too low for some of the server photos I wanted to add. No problem, just increase the limit right? Well no. Since the site was still in "Safe Mode" I couldn't change any of the advanced functions. The solution? Switch to Free Mode, billed as a simple process of a few clicks. Lets do this then! Clicked the deceptively easy "Switch to Free Mode" button prepared for a few clicks and getting on with my day. Filled out the information, set the flags I wanted, clicked go.....and it failed. That's fine, it went back to safe mode so I can just retry, right? Fails again. Third times the charm? Nope.At this...
This topic first appeared in the Spiceworks Community

Preffered and alternate DNS details

Dear Team,I have Many DC/ADC in my domain and of course they are DNS servers also.But i recently noticed that some of the DC DNS does't have correct preferred/Alternate DNS. Is there any way through power shell or netsh where in i can know all the
server in which DNS is installed in my domain along with the assigned preferred and alternate DNS details.So i can have a bird's view.
Senior System Engineer.

Thanks anyways..I have other question also ..i see many people who responds have some points added..like in your case it's 1470..what are this and who assigns this..what is the concept of Vote.?This question is eating my brain since few months..Any
information would be great help..
Senior System Engineer.
You get recognition points by contributing posts the community finds valuable.
Points are not effort based but instead based on quality as perceived by the community.
Contributing Answers: Replies the community decides are answers get you points. Marking your own replies as answers does not give you points.
Contributing Helpful Posts: Contributing replies the community votes as helpful get you points.
Asking Good Questions: Users that ask valuable (helpful and/or popular) questions will be rewarded additional points.
Bonus Points: Users can also gain extra points by contributing valuable contributions quickly or when their contributions are deemed valuable by the users asking
the questions.
Source:
http://social.technet.microsoft.com/wiki/contents/articles/7359.forums-help-faq.aspx#315
More questions take a look at TechNet Forums FAQ:
http://social.technet.microsoft.com/wiki/contents/articles/7359.forums-help-faq.aspx
The best answer to your brain stop been eaten haha (:
Sergio Figueiredo
Microsoft Certified Solutions Associate

Lync 2013 Edge DNS config understanding

Hey guys,
I just set up our Lync 2013 frontend server, which is running fine internally. The Edge is runing as well, but I still have to do the port forwardings in the firewall and the external DNS configuration. But I got an understanding issue.
I followed these instructions. "Edge server IP as specified in setup wizard" is very clear, but what exactly is meant with "Lync
Reverse Proxy IP"
Just to explain a bit the infrastructure, we got a Sophos UTM as firewall. In total we have attached 4 external IPs to the Sophos. For sure the external IP's on the FW are NATed to the 192.168.50.X of the external Edge interface.
80.123.250.160 sip.mydomain.com
80.123.250.161
webconf.mydomain.com
80.123.250.162 av.mydomain.com
80.123.250.163 mail.mydomain.com and general stuff
So if I understand it correct, it should just be one
of the IP's which are connected to the FW, so I could just take the 80.123.250.160 or am I missing something?
Thanks in advance.
Kind regards,
Chris

The Lync Reverse Proxy IP refers to a reverse proxy such as IIS ARR
http://blogs.technet.com/b/nexthop/archive/2013/02/19/using-iis-arr-as-a-reverse-proxy-for-lync-server-2013.aspx that is a separate server than the Edge server and cannot be collocated on the Edge server. It proxies web traffic to the external web
services FQDN, and simple URLs on your Front End server from the Internet.
If you only have 4 IPs, but are using a reverse proxy to NAT traffic to mail.mydomain.com, you could potentially also use this same reverse proxy but you'll need either a wildcard certificate or a certificate that includes all the names you'll need for the
SAN. If you're not using a reverse proxy and instead are directly transferring traffic to mail.mydomain.com, I'd suggest setting up an IIS ARR server for this purpose and using the same reverse proxy to transfer all traffic.
If that's not possible, you may have to use a single external IP for your edge (.160) and use another (.161) for your Lync reverse proxy.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications
This forum post is based upon my personal experience and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Difference between mobile web dynpro and simple web dynpro application

Hi Everyone,
Can anyone pls let me know what's the difference b/w mobile web dynpro application and an offline or simple web dynpro application.
Thank U!!
Ravi Aswani

Hi ,
Mobile WebDynpro
The SAP Web Application Server allows direct online access to Web Dynpro applications using mobile devices. As part of the SAP Web Application Server, Web Dynpro provides a development and runtime environment with which you can quickly and simply create professional user interfaces for desktop PCs or for mobile devices. An appropriate infrastructure and renderer classes are provided for developing mobile Web Dynpro applications for Pocket PCs as well as for BlackBerry Wireless Handhelds and Nokia Series 80 devices.
http://help.sap.com/erp2005_ehp_03/helpdata/EN/fa/100d4113eff16fe10000000a1550b0/frameset.htm
WebDynpro Java
Web Dynpro is a client-independent programming model of the SAP NetWeaver technology platform for developing user interfaces for professional business applications. It is based on the model view controller paradim which ensures that the business logic is separated from the presentation logic. This architecture is visible in the Web Dynpro perspective of the SAP NetWeaver Developer Studio (NWDS).
Web Dynpro helps you with the development of Web applications by:
·        Ensuring platform-independence with the meta model approach
·        Minimizing the implementation effort through declarative programming
·        Supporting a structured design process by applying the model view controller paradigm
·        Providing reuse and better maintainability by using components
·        Providing graphical support with tools in the Web Dynpro perspective
·        Providing the SAP NetWeaver Java Development Infrastructure (NWDI) which supports team work with different services such as source code versioning and the Central Build Service.
http://help.sap.com/erp2005_ehp_03/helpdata/EN/fa/100d4113eff16fe10000000a1550b0/frameset.htm
Thanks
Suresh
Edited by: Suresh Mandalapu on Sep 2, 2008 11:07 AM

Difference between connection pooling and simple connection

Anybody please tell me what is the Difference between connection pooling and simple connection and also where we define connection pooling and how.
Thanks
Please reply soon
amitindia

Creating and closing connection to the database is a relatively slow process. Equally connections use database resources so you can't just open as many as you want.
A connection pool maintains a number of open connections throughout the lifetime of the application. Instead of opening and closing the connections your application just "borrows" them from the pool when they're needed.
If the pool runs out of connections it will usually create new ones as needed until you reach some predefined upper limit.
A good connection pool will also manage connections which have failed for any reason, and report code which fails to return connections to the pool (ie connection leaks).
The number of connections created at startup is referred to as the "low water mark" and the maximum number that the pool will allow to be opened at any given time is the "high water mark". If no connections are available client code will generally block until one is released.
If by "defined" you mean where can you get a working implementation then your database or application server vendor is likely to provide one. Also the Apache Jakarta Commons includes [url http://jakarta.apache.org/commons/dbcp/]an implementation which you can use with any JDBC driver.
Dave.

Quick and Simple DNS Config

Similar Messages

Maybe you are looking for