Sponsored Content
Top Forums UNIX for Advanced & Expert Users System cutover - name resolution Post 15797 by rwb1959 on Tuesday 19th of February 2002 02:56:10 PM
Old 02-19-2002
Assuming you have an internal DNS, you could
add a "CNAME" type entry into your zone files
so that "seq2" will map to "palprod". This
would at least be realtively clean and localized.

Something like...

palprod IN A 192.168.254.200.
seq2 IN CNAME palprod.myco.com.
 

8 More Discussions You Might Find Interesting

1. UNIX Desktop Questions & Answers

Resolution..??

When i start my pc after the installation of suse linux it ask me for resolution but not for graphical interface, for console, can i run a command to change it again? Thanx! (3 Replies)
Discussion started by: Linux_fan
3 Replies

2. UNIX for Advanced & Expert Users

Monitor Resolution

My machine (Sun Blade 100) has just had it's OS reinstalled (solaris 8). For some reason the monitor resolution has changed (decreaded so that I have less monitor real esate). Does anybody know the command to change monitor resolution in Solaris? Cheers AreaMan (2 Replies)
Discussion started by: AreaMan
2 Replies

3. UNIX for Advanced & Expert Users

Monitor Resolution

Guys, We are going to order the wide screen monitor with 1920*1200 resolution for one U60 in our client side, that their current graphic card is Elite3D-m6 and the higher resolution which this card supports is 1280*1024. I just want to make sure wehther we are able to work with this monitor via... (1 Reply)
Discussion started by: nikk
1 Replies

4. Solaris

DNS name resolution

Hi, I got solaris 10 installed on a E250 and i am expericing issues resolving dns. from some research i think it's becuase where i haven't set-up NIS and i don't intend too as i am just setting up a box to poke communigate pro. Any help or advice please? Thanks in advance Alan (1 Reply)
Discussion started by: e250user
1 Replies

5. IP Networking

Problem with name resolution?

I have an AIX4.3 box on our subnet, called LIMEST3.OURDOMAIN.CO.UK, with IP address 10.103.1.13 It has the following entry in its own /etc/hosts: 10.103.1.13 limest3 limest3.ourdomain.co.uk Now, if I ping limest3.ourdomain.co.uk or ping 10.103.1.13, the result is instant. However if I ping... (4 Replies)
Discussion started by: grimbleshanks
4 Replies

6. UNIX for Dummies Questions & Answers

screen resolution for a SPARC system

I have installed Solaris 10 on SPARC system (Ultra 5) And I'm using Acer AL1715 LCD monitor. The screen resolution is not just right. How to change the resolution Thanks in advance. (1 Reply)
Discussion started by: chaandana
1 Replies

7. Red Hat

data resolution

hi all after going through ext3 file system , i understood that data resolution for ext3 FS is 1 second...can i increase it 2 second...? any idea..? (3 Replies)
Discussion started by: sagar_md
3 Replies

8. Solaris

Screen Resolution

Hi all. I have a very peculiar problem in Solaris 10. The output of the m64config -prconf command with regards the Card Adapter is the following. Card possible resolutions: 720x400x85, 640x480x60, 640x480x72, 640x480x75 800x600x56, 800x600x60, 800x600x72, 800x600x75, 1024x768x60 ... (0 Replies)
Discussion started by: lynxman
0 Replies
SHOREWALL-EXCLUSION(5)						  [FIXME: manual]					    SHOREWALL-EXCLUSION(5)

NAME
exclusion - Exclude a set of hosts from a definition in a shorewall configuration file. SYNOPSIS
!address-or-range[,address-or-range]... !zone-name[,zone-name]... DESCRIPTION
The first form of exclusion is used when you wish to exclude one or more addresses from a definition. An exclaimation point is followed by a comma-separated list of addresses. The addresses may be single host addresses (e.g., 192.168.1.4) or they may be network addresses in CIDR format (e.g., 192.168.1.0/24). If your kernel and iptables include iprange support, you may also specify ranges of ip addresses of the form lowaddress-highaddress No embedded whitespace is allowed. Exclusion can appear after a list of addresses and/or address ranges. In that case, the final list of address is formed by taking the first list and then removing the addresses defined in the exclusion. Beginning in Shorewall 4.4.13, the second form of exclusion is allowed after all and any in the SOURCE and DEST columns of /etc/shorewall/rules. It allows you to omit arbitrary zones from the list generated by those key words. Warning If you omit a sub-zone and there is an explicit or explicit CONTINUE policy, a connection to/from that zone can still be matched by the rule generated for a parent zone. For example: /etc/shorewall/zones: #ZONE TYPE z1 ip z2:z1 ip ... /etc/shorewall/policy: #SOURCE DEST POLICY z1 net CONTINUE z2 net REJECT /etc/shorewall/rules: #ACTION SOURCE DEST PROTO DEST # PORT(S) ACCEPT all!z2 net tcp 22 In this case, SSH connections from z2 to net will be accepted by the generated z1 to net ACCEPT rule. In most contexts, ipset names can be used as an address-or-range. Beginning with Shorewall 4.4.14, ipset lists enclosed in +[...] may also be included (see shorewall-ipsets[1] (5)). The semantics of these lists when used in an exclusion are as follows: o !+[set1,set2,...setN] produces a packet match if the packet does not match at least one of the sets. In other words, it is like NOT match set1 OR NOT match set2 ... OR NOT match setN. o +[!set1,!set2,...!setN] produces a packet match if the packet does not match any of the sets. In other words, it is like NOT match set1 AND NOT match set2 ... AND NOT match setN. EXAMPLES
Example 1 - All IPv4 addresses except 192.168.3.4 !192.168.3.4 Example 2 - All IPv4 addresses except the network 192.168.1.0/24 and the host 10.2.3.4 !192.168.1.0/24,10.1.3.4 Example 3 - All IPv4 addresses except the range 192.168.1.3-192.168.1.12 and the network 10.0.0.0/8 !192.168.1.3-192.168.1.12,10.0.0.0/8 Example 4 - The network 192.168.1.0/24 except hosts 192.168.1.3 and 192.168.1.9 192.168.1.0/24!192.168.1.3,192.168.1.9 Example 5 - All parent zones except loc any!loc FILES
/etc/shorewall/hosts /etc/shorewall/masq /etc/shorewall/rules /etc/shorewall/tcrules SEE ALSO
shorewall(8), shorewall-accounting(5), shorewall-actions(5), shorewall-blacklist(5), shorewall-hosts(5), shorewall_interfaces(5), shorewall-ipsets(5), shorewall-maclist(5), shorewall-masq(5), shorewall-nat(5), shorewall-netmap(5), shorewall-params(5), shorewall-policy(5), shorewall-providers(5), shorewall-proxyarp(5), shorewall-rtrules(5), shorewall-routestopped(5), shorewall-rules(5), shorewall.conf(5), shorewall-secmarks(5), shorewall-tcclasses(5), shorewall-tcdevices(5), shorewall-tcrules(5), shorewall-tos(5), shorewall-tunnels(5), shorewall-zones(5) NOTES
1. shorewall-ipsets http://www.shorewall.net/manpages/shorewall-ipsets.html [FIXME: source] 06/28/2012 SHOREWALL-EXCLUSION(5)

Featured Tech Videos

All times are GMT -4. The time now is 11:12 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy